On Jun 4, 2011, at 17:23, Mark Hattam wrote: > Having just done port updates for dbus and dovecot2 this evening, they both > printed out similar guidance messages about startup items. > > But I don't understand why dbus uses "launchctl load" whereas dovecot uses > "port load" ... is there a difference?
"port load" is a wrapper around "launchctl load -w". It's simply a convenience so you don't have as much to type (or remember). Ports that use standard MacPorts startupitem commands will automatically print a message explaining how you can use "port load" to load it, as you showed below with dovecot2. dbus has two startup items, so it can't use MacPorts code to create them, and furthermore needs one of them started as root, the other not as root. Therefore it prints its own instructions. > ############################################################################ > # Startup items have been generated that will aid in > # starting dbus with launchd. They are disabled > # by default. Execute the following command to start them, > # and to cause them to launch at startup: > # > # sudo launchctl load -w > /Library/LaunchDaemons/org.freedesktop.dbus-system.plist > # launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist > ############################################################################ > > > ########################################################### > # A startup item has been generated that will aid in > # starting dovecot2 with launchd. It is disabled > # by default. Execute the following command to start it, > # and to cause it to launch at startup: > # > # sudo port load dovecot2 > ########################################################### _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
