[MacPorts] #44475: doc-issue: startupitem_install no

[MacPorts]

#44475: doc-issue: startupitem_install no
------------------------------+--------------------
  Reporter:  ora.et.labora@…  |      Owner:  jmpp@…
      Type:  defect           |     Status:  closed
  Priority:  Normal           |  Milestone:
 Component:  website          |    Version:  2.3.1
Resolution:  fixed            |   Keywords:
      Port:                   |
------------------------------+--------------------

Comment (by ora.et.labora@…):

 ''They are not equivalent. The first disables creation of StartupItems
 completely; you’d use this if you didn’t want them available at all for
 some reason. The second only disables symlinking them into /Library and is
 usually used to prevent conflicts between two parallel MacPorts
 installations; I believe you can still have launchd load them by passing
 the full filenames to launchctl(1), although I’m not 100% sure.''

 Thanks for the clarification.

 Btw, I can confirm that passing full file name (absolute path) to
 launchctl works. It is rather the other way round, I never had success in
 doing


 {{{
 $ ls /Library/LaunchDaemons
 [..]
 org.macports.mysql56-server.plist@

 $ launchctl load org.macports.mysql56-server
 launchctl: Couldn't stat("org.macports.mysql56-server"): No such file or
 directory

 $ launchctl load org.macports.mysql56-server.plist
 launchctl: Couldn't stat("org.macports.mysql56-server.plist"): No such
 file or directory

 $  launchctl load -D all org.macports.mysql56-server.plist 2>&1 | head
 launchctl: Couldn't stat("org.macports.mysql56-server.plist"): No such
 file or directory
 [..]
 bind(): Address already in use
 [..]
 com.apple.AirPlayXPCHelper: Already loaded

 $ launchctl load -D all org.macports.mysql56-server 2>&1 | head
 launchctl: Couldn't stat("org.macports.mysql56-server"): No such file or
 directory
 [..same as above ..]
 }}}

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