On Sep 18, 2010, at 13:35, [email protected] wrote:

> Revision: 71637
>          http://trac.macports.org/changeset/71637
> Author:   [email protected]
> Date:     2010-09-18 11:35:27 -0700 (Sat, 18 Sep 2010)
> Log Message:
> -----------
> Added startupitem definition for launchd to auto-load beanstalkd on startup. 
> Closes #26521

> +startupitem.create      yes
> +startupitem.executable  ${prefix}/bin/beanstalkd -u nobody
> +
> +post-activate {
> +    ui_msg "###########################################################"
> +    ui_msg "# To launch beanstalkd manually, run:"
> +    ui_msg "# "
> +    ui_msg "# sudo launchctl load -w 
> /Library/LaunchDaemons/org.macports.beanstalkd.plist"
> +    ui_msg "# "
> +    ui_msg "# and to stop beanstalkd, run:"
> +    ui_msg "# "
> +    ui_msg "# sudo launchctl unload -w 
> /Library/LaunchDaemons/org.macports.beanstalkd.plist"
> +    ui_msg "###########################################################"
> +}

Adding "startupitem.create yes" to the portfile already causes MacPorts to 
print instructions for using the launchd plist, so these additional 
instructions you've added here should be unnecessary. If you believe the 
instructions MacPorts automatically adds are insufficient, it would be better 
to improve the instructions in MacPorts base rather than making a special 
exception here just for this port.



_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Reply via email to