Patch to make DBus services directory path configurable at compile time and store it's location as an explicit variable in dbus's pkg-config file

John (J5) Palmieri johnp at
Thu Mar 16 19:20:43 PST 2006

Looks good.  Patch committed.

On Fri, 2006-03-17 at 01:24 +0100, Milosz Derezynski wrote:
> The reason (although a not very convincing one admittedly) for having
> it configurable at build time is that the session.conf file should be
> probably left alone to most parts after installation, especially the
> services path. Now it's obvious that this is in practical terms mostly
> a rather synthetic semantical construct since there is basically no
> difference to whether one specifies a custom path with configure or
> edits the session.conf file after installation (if it's not enough
> having a different prefix), since if one wants to do that (have a
> different services dir path) one'd do that anyway regardless of
> whether you "should or shouldn't" do it.
> I'm attaching a new patch that merely adds a pkgconfig variable with
> the services directory path, and i've renamed it to
> "session_bus_services_dir", and also added the output of this path to
> the configure summary (just taking the chance, it can't hurt to know
> this when you're compiling dbus).
> On 3/17/06, Havoc Pennington <hp at> wrote:
>         Hi,
>         I understand the purpose of putting the services dir in
>         the .pc file,
>         but what is the rationale for making it configurable in
>         People can just edit the session.conf and .pc file if they
>         want to
>         change it (also, why would they want to change it at all).
>         Anyhow, in
>         general I see no point in adding config file elements to
>         just edit the config file. That's what config files are for. 
>         I think it'd be important to name the pkg-config variable
>         something with
>         "session" in it.
>         My view on the session.conf file issue is that changing that
>         isn't
>         really supported; it's only in the config file to support
>         "nonstandard" 
>         bus instances, or possibly someone might have the session bus
>         look
>         in /opt or something in a local installation.
>         Havoc
> _______________________________________________
> dbus mailing list
> dbus at

More information about the dbus mailing list