Startupitems don't work as advertised

[Ryan Schmidt]

On Jun 1, 2007, at 16:03, Chris Pickel wrote:

> On 01 Jun, 2007, at 15:23, James Berry wrote:
>
>> or (b) Default the key to true, and leave the emitted text as it is.
>
> Actually, this introduces another problem; asking launchctl to load  
> a disabled script (as many ports now do) won't cause it to run. To  
> fix this, the text will need to be edited in all such ports. It  
> should tell the user to edit the launchd script and change that flag.

What? No no no. That's what the -w flag to launchctl is for -- to add  
or remove the "disabled" key. And port already outputs instructions  
which tell you to use -w when calling launchctl. From the first mail  
in this thread:

> ###########################################################
> # A startup item has been generated that will aid in
> # starting XXXX with launchd. It is disabled
> # by default. Execute the following command to start it,
> # and to cause it to launch at startup:
> #
> # sudo launchctl load -w /Library/LaunchDaemons/ 
> org.macports.XXXX.plist
> ###########################################################