[MacPorts] #14223: p5-mail-spamassassin upgrade overwrites the user's /Library/LaunchDaemons/org.macports.spamd.plist

[MacPorts]

#14223: p5-mail-spamassassin upgrade overwrites the user's
/Library/LaunchDaemons/org.macports.spamd.plist
----------------------------------+-----------------------------------------
  Reporter:  vinc17 at macports.org  |       Owner:  simon at macports.org
      Type:  defect               |      Status:  new               
  Priority:  Normal               |   Milestone:  Port Bugs         
 Component:  ports                |     Version:  1.6.0             
Resolution:                       |    Keywords:                    
----------------------------------+-----------------------------------------
Comment (by vinc17 at macports.org):

 Replying to [comment:5 dluke at macports.org]:
 > It is installed to enable the end user to easily 'activate' the
 automatic startup (launchctl load -w foo.plist).

 But the {{{launchctl load -w foo.plist}}} is not remembered after a
 reboot. So, I don't think this is easy. Also, if the user wants to do
 {{{launchctl load -w foo.plist}}}, I suppose he can still do it if the
 plist is in the doc directory (or in some other directory that makes clear
 that the files must not be modified by the user).

 > The way the current startupitem code works, the plist will be
 recreated/replaced upon upgrade.

 The replace script should be able to detect when the file has been
 modified. The current solution is broken. BTW, there has been a similar
 discussion in the macports-dev (''Updating macports.conf'').

 > Perhaps we should update the documentation to make this more clear?

 The current way is still confusing as it breaks conventions.

 > In any event, it's not a bug for this particular port (it's either a
 documentation bug, or a base bug).

 Yes, perhaps a base bug.

-- 
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14223#comment:6>
MacPorts </projects/macports>
Ports system for Mac OS