#44497: Change port load to use MacPorts plists directly ------------------------------+-------------------------------- Reporter: ora.et.labora@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: base | Version: 2.3.1 Resolution: | Keywords: Port: | ------------------------------+-------------------------------- Comment (by ora.et.labora@…): Replying to [comment:1 larryv@…]:
Rather, the following should happen (or be documented):
{{{ launchctl load -w $MP_PREFIX/etc/LaunchDaemons/org.macports.${port}.plist }}}
But launchd would not be able to automatically start the job at boot/login, which is probably the behavior most users expect.
Be aware that this is a different subject! My proposal above would not change the expected behaviour, i.e. if a sym link from /Library/LaunchDaemons into /opt/local/etc/LaunchDaemons is present, then launchd boots that process as usual. With my proposal however, even if I have configured `startupitem_install no` in macports.conf, I can still do a `port load $portname` to launch a process. The current behaviour is that (a manua) removal of a symbolic link in /Library/LaunchDaemons renders port load|unload broken. ----
In addition then, there is also not need to create links in /Library/Launch* (outside of $MP_PREFIX)
Perhaps it's best not to continue with this proposal then. I just expect that no software is about to run after having *installed* software. It's just me who want to be in control when I'm going to run software. I would also be very happy if the general rule is that *absolutely nothing* is installed or changed outside of `/opt/local` (except the installation folder of MacPorts itself). -- Ticket URL: <https://trac.macports.org/ticket/44497#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X