[MacPorts] #17950: dbus patched with launchd support and version dump

[MacPorts]

#17950: dbus patched with launchd support and version dump
---------------------------------+------------------------------------------
  Reporter:  jonas.baehr@…       |       Owner:  macports-tickets@…                   
      Type:  enhancement         |      Status:  reopened                             
  Priority:  Normal              |   Milestone:  Port Enhancements                    
 Component:  ports               |     Version:  1.7.0                                
Resolution:                      |    Keywords:  launchd kde4 x11                     
      Port:  dbus                |  
---------------------------------+------------------------------------------

Comment(by mta@…):

 Replying to [comment:36 jonas.baehr@…]:
 > I think the solution is to ask launchd for the address if
 DBUS_SESSION_BUS_ADDRESS is not set, ''or it contains a launchd:
 address''. The latter is currently not the case. I'll fix that.

 It's not clear to me that it's that simple, although I don't understand
 this code well enough to be sure.  The "launchd:..." address comes from
 _dbus_server_new_for_socket which constructs it from the string
 "launchd:key=session" passed to it from
 _dbus_server_listen_platform_specific and a guid created and appended by
 _dbus_server_init_base.  Then this is passed, via the
 DBUS_SESSION_BUS_ADDRESS environment variable, to the child configd-2
 process.  It's not obvious that having that child process get the
 DBUS_LAUNCHD_SESSION_BUS_SOCKET from launchctl will return the correct
 socket name.  What's the guid good for?  Should it be used some way to
 look up the socket?  Should the server be doing this and assigning the
 correct Unix socket name to DBUS_SESSION_BUS_ADDRESS?  It's questions like
 this which kept me from implementing a fix.

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