/Library/LaunchDaemons/org.macports.mysql5.plist
/opt/local/etc/LaunchDaemons/org.macports.mysql5/org.macports.mysql5.plist
file /Library/LaunchDaemons/org.macports.mysql5.plist
/Library/LaunchDaemons/org.macports.mysql5.plist: symbolic link to `/opt/local/etc/LaunchDaemons/org.macports.mysql5/org.macports.mysql5.plist'
The symlink will allow to keep the file(s) MacPorts needs in the /opt/local tree and still get them to fire at boot time.
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
##
##########