[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:46 jonas.baehr@…]:
 > My hotfix in [#comment:42] is also valid, since only children of launchd
 can talk to launchd via IPC. That means the env var is always present, but
 also that it's impossible to start dbud-daemon manually if it should
 listen on a "launchd:"-address. This limitation lays in the design of
 launchd and is not a problem with the patch.

 I don't think this is quite right.  There is a tree of processes under
 launchd.  Any process in this tree can talk to launchd and get the value
 of the environment variable using code like that in
 _dbus_lookup_session_address_launchd.  However the environment variable
 itself is only in the environment of the dbus process and its descendants.
 I don't know if this matters much, but it means that clients started by
 siblings or cousins of the dbus process don't have the environment
 variable giving the dbus socket in their environment.

 When I logon the dbus process gets started.  If I subsequently start (for
 example) a terminal process from which I start a dbus client, it can't
 find the dbus started by launchd unless it uses code like that in
 _dbus_lookup_session_address_launchd.

 > Please test. I think this ticket can be closed since the new version of
 the patch should solve all of the above issues.

 I suspect it works for most of the cases that matter.  I'll give it a try
 and get back to you.

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