On Sep 30, 2007, at 12:18, paul beard wrote:
Conversely, you can add the appropriate lines to launchd.conf and
get things going.
more /etc/launchd.conf
launchctl load /opt/local/etc/LaunchDaemons/org.macports.dbus/
org.macports.dbus.p
list
launchctl load /opt/local/etc/LaunchDaemons/org.macports.apache2/
org.macports.apa
che2.plist
launchctl load /opt/local/etc/LaunchDaemons/org.macports.mysql5/
org.macports.mysq
l5.plist
I would vote for MacPorts to take the latter approach, with the
post-install message explaining that
########
## To get the application to run at boot time,
## echo launchctl load /opt/local/etc/LaunchDaemons/
org.macports.mysql5/org.macports.mysql5.plist >> /etc/launchd.conf
##
##########
Feel free to make a proposal to the macports-dev list if you feel
strongly about this. The current approach works, so you should
explain why your approach is better (and if there are any reasons why
it might be worse).
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
