[MacPorts] #37474: dbus: eliminate the need to manually run launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist (was: eliminate the need to manually run launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist)

[MacPorts]

#37474: dbus: eliminate the need to manually run launchctl load -w
/Library/LaunchAgents/org.freedesktop.dbus-session.plist
--------------------------+------------------------
  Reporter:  cginsburg@…  |      Owner:  mcalhoun@…
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.1.2
Resolution:               |   Keywords:
      Port:  dbus         |
--------------------------+------------------------
Changes (by ryandesign@…):

 * owner:  macports-tickets@… => mcalhoun@…
 * port:   => dbus


Comment:

 It isn't our custom to start launchdaemons for you. Launchd plists that
 are installed automatically using
 [http://guide.macports.org/chunked/reference.startupitems.html
 startupitem.create] are not started for you; MacPorts just prints a
 message telling you how to do so. For most such ports, the launchd plists
 start servers that require some manual configuration before they're
 started.

 dbus is unusual in that org.freedesktop.dbus-session.plist is installed
 manually, not using startupitem.create, and no configuration is required,
 so there would be value in having things automatically started. However I
 don't think we are able to do so. As the notes say:

 {{{
 $ port notes dbus
 dbus has the following notes:
 ############################################################################
   # Startup items have been generated that will aid in
   # starting dbus with launchd. They are disabled
   # by default. Execute the following command to start them,
   # and to cause them to launch at startup:
   #
   # sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-
 system.plist
   # launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-
 session.plist
 ############################################################################
 }}}

 So as you see, dbus-system needs to be started as root, and dbus-session
 needs to be started as your user, and furthermore starting dbus-session
 needs to be done individually by every user who wants to use dbus-
 compatible software. MacPorts is started as root (using sudo) and then
 drops privileges to the "macports" user. There is no time at which
 MacPorts is running as your user account, so there's no way for MacPorts
 to start dbus-session for you.

-- 
Ticket URL: <https://trac.macports.org/ticket/37474#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS