[MacPorts] #44475: doc-issue: startupitem_install no
#44475: doc-issue: startupitem_install no -----------------------------+-------------------- Reporter: ora.et.labora@… | Owner: jmpp@… Type: defect | Status: new Priority: Normal | Milestone: Component: website | Version: 2.3.1 Keywords: | Port: -----------------------------+-------------------- https://guide.macports.org/chunked/installing.macports.html states, that "startupitem_install" should be placed into $MP_PREFIX/etc/macports/sources.conf if no start-up items are to be placed into /Library/*. Is that really correct? After having done so, I'm getting: {{{ $ port version Warning: /opt/local/etc/macports/sources.conf specifies invalid source 'startupitem_install no', ignored. Version: 2.3.1 }}} I assume that $MP_PREFIX/opt/local/etc/macports/macports.conf must be the proper location. '''Side issue:''' However, why the need for an extra property? Aren't those two property settings equivalent? {{{ startupitem_type none startupitem_install no }}} But then: what does none really mean? The documentation is rather poor on this. Of course I do want to have the startup-items generated somewhere below $MP_PREFIX/opt/local. I just don't want that they are activated by default. -- Ticket URL: <https://trac.macports.org/ticket/44475> MacPorts <http://www.macports.org/> Ports system for OS X
#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: | ------------------------------+-------------------- Changes (by larryv@…): * status: new => closed * resolution: => fixed Comment: Replying to [ticket:44475 ora.et.labora@…]:
I assume that $MP_PREFIX/opt/local/etc/macports/macports.conf must be the proper location.
You’re right; I’ve corrected the Guide in r122772.
However, why the need for an extra property? Aren't those two property settings equivalent?
{{{ startupitem_type none startupitem_install no }}}
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. -- Ticket URL: <https://trac.macports.org/ticket/44475#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#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
#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 larryv@…): Replying to [comment:3 ora.et.labora@…]:
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
To be honest, I don’t really do much with launchd directly. If you’re curious about this behavior in general, you could inquire on the [[MailingLists|macports-users mailing list]]. If you only care about loading MacPorts-provided jobs, try `port load`: {{{ % sudo port load mysql56-server }}} -- Ticket URL: <https://trac.macports.org/ticket/44475#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts