[MacPorts] #44497: port load issue

[MacPorts]

#44497: port load issue
-----------------------------+---------------------
 Reporter:  ora.et.labora@…  |      Owner:  markd@…
     Type:  enhancement      |     Status:  new
 Priority:  Normal           |  Milestone:
Component:  guide            |    Version:  2.3.1
 Keywords:                   |       Port:
-----------------------------+---------------------
 The manual page of port load states:

 {{{
    load
      Provides a shortcut to using launchctl to load a port's daemon (as
 installed in /Library/LaunchDaemons).  It runs:

            launchctl load -w
 /Library/LaunchDaemons/org.macports.${port}.plist
 }}}

 Is this correct? Cause it does not make much sense having more than one
 MacPorts installation. Rather, the following should happen (or be
 documented):

 {{{
            launchctl load -w
 $MP_PREFIX/etc/LaunchDaemons/org.macports.${port}.plist
 }}}

 This way, the "port" command determines MP_PREFIX and starts up the proper
 daemon.

 In addition then, there is also not need to create links in
 /Library/Launch*  (outside of $MP_PREFIX), hence also no need for those
 two macports.conf properties:

 {{{
 startupitem_type
 startupitem_install
 }}}

 Property startupitem_type is not necessary as just always all startup
 items can (and should) be generated below $MP_PREFIX. The other property -
 startupitem_install - is not neccessary because not conflicts can be
 created.

 If a user would like to auto start-up a daemon, then he/she would need to
 create that symlink link herself or a further subcommand of "port" could
 do the job. In addition, if a port is going to be removed, a symlink check
 could be run which would warn a user if a dangling symlink would be the
 result of a port removal.

-- 
Ticket URL: <https://trac.macports.org/ticket/44497>
MacPorts <http://www.macports.org/>
Ports system for OS X