dbus and launchd

Ryan Schmidt ryandesign at macports.org
Wed Jan 20 22:12:17 PST 2010

On Jan 20, 2010, at 19:32, Dan Ports wrote:

> 3) Both launchd jobs have launch-on-demand disabled, I think because it
>   didn't work correctly on Tiger. Now that Tiger is borderline
>   unsupported, should we reconsider this? (We can make it a platform
>   variant to keep from breaking TIger unnecessarily)
>   Moving to on-demand would also make it pretty reasonable in my view
>   to enable the launchd jobs on port install, eliminating the need for
>   users to run two launchctl load commands (of which one needs to be
>   run as root and the other *not* as root!)

On-demand launching has been requested in some of my ports (see tickets) but I declined, saying it should be handled in base. I haven't used on-demand plists so I don't know about any bugs involved. Are there any downsides to on-demand launching? Should it be an option in macports.conf?

More information about the macports-dev mailing list