Bug 16791 - shell expansion for <listen>
Summary: shell expansion for <listen>
Status: RESOLVED DUPLICATE of bug 14259
Alias: None
Product: dbus
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: Other All
: high enhancement
Assignee: Havoc Pennington
QA Contact: John (J5) Palmieri
Depends on:
Reported: 2008-07-21 06:45 UTC by Darrell Schiebel
Modified: 2008-07-21 06:52 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Darrell Schiebel 2008-07-21 06:45:29 UTC
I've started using dbus on OSX, and OSX sets the environment variable TMPDIR for each user as a temporary directory for each users session. The configure script for DBUS picks up on the fact that TMPDIR is defined, and it sets this directory as the target directory for the session <listen> named pipe. This has two problems:

    (1) other users do not have the same temporary directory as I do
    (2) my temporary directory will change with each login (I believe) and certainly with each reboot

To resolve these problems, I introduced shell expansion to <listen>, but only when the "expand_env" attribute is set to "yes". So under Mac OSX, the session.conf file can contain:

    <listen expand_env="yes">unix:tmpdir=$(TMPDIR)</listen>

All shell variables must be defined and only the "$(NAME)" syntax is supported. Backslash can be used to escape characters.

The only thing I've left undone is adding a "unsupported" stub or something similar for non-Unix platforms. Attached is a tarfile with the files I modified (these modifications were against version 1.1.20).

Please consider adding this feature to the next version of DBUS.

Darrell Schiebel
Comment 1 Colin Walters 2008-07-21 06:52:16 UTC
See also Bug #14259 which adds explicit support for Mac OS X to DBus.  I believe once that bug is finished this change will not be necessary.

*** This bug has been marked as a duplicate of bug 14259 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.