RFE: launchctl .plist files can/should installed w/in the /opt/local tree

[paulbeard@…]

Rather than put stuff in /opt/local and link to it from /Library, it's possible to install .plist files in /opt/local/LaunchDaemons and call them from /etc/launchd.conf. if the ports are removed or something happens to the MacPorts installation, a couple of lines of text in a file is tidier than crufty dead links all over the place. And it maintains the idea of minimal transgressions outside the /opt sandbox.

launchctl load -w /opt/local/etc/LaunchDaemons/org
.macports.mysql5/org.macports.mysql5.plist
launchctl load -w /opt/local/etc/LaunchDaemons/org.macports.apache2/org.macports.apache2.plist

[paulbeard@…]

Do this help at all?

--- /tmp/Portfile       2007-06-25 20:30:20.000000000 -0700
+++ Portfile    2007-03-02 13:51:15.000000000 -0800
@@ -70,11 +70,6 @@
                ${worksrcpath}/support/envvars-std
 }
 
-post-install {
-       # add commands to launchd.conf
-       echo "# apache2 startup directive added by MacPorts" >> /etc/launchd.conf
-       echo "launchctl load -w /opt/local/etc/LaunchDaemons/org.macports.apache2/org.macports.apache2.plist" >> /etc/launchd.conf
-
 post-destroot {
        set confDir ${destroot}${prefix}/apache2/conf
        file rename -force ${confDir}/httpd.conf ${confDir}/httpd.conf.sample

[nox@…]

LaunchDaemons plist files are installed in ${prefix}, there is just a symlink put in /Library/LaunchDaemons

[jberry@…]

The approach we take at present (putting a symlink in /Library/LaunchDaemons), seems cleaner than writing to /etc/launchd.conf.