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

Gary Kramlich grim at
Thu Mar 16 11:34:31 PST 2006

> Hey everyone,
> The attached patch adds the option to set the directory/path for .service
> files as a configure withval, as well as it encodes the services dir as an
> explicit variable into the .pc file.In case this option is not specified,
> the behaviour of the build system is unchanged to previous versions of
> dbus
> (i.e. it will default to $datadir/dbus-1/services).
> This was agreed upon recently on IRC; although the services dir will be
> probably always just $datadir/dbus-1/services, we still agreed it would be
> better and less hackish if other's/.in's could use
> "pkg-config
> --variable=services_dir" directly instead of having to acquire the prefix
> and then, technically seeing, assume that the services dir is
> $prefix/share/dbus-1/services.
> Attached find the file made against CVS from around Thu Mar 16 17:58:13
> 2006
> Regards,
> Milosz
> PS: I just stumbled upon a problematic situation doing this: The
> session.conf file is in theory editable, and thus the services dir can be
> changed, but that won't automatically change the .pc file.
> More problematic: what if someone has a dbus installation, a dozen
> programs
> install their .service files into the given services dir, and then someone
> goes and edits the session.conf file and changes that path? I guess that's
> something someone shouldn't do in the first place, but is it anywhere
> officially advised not to do so, etc? I mean, are there any regulations in
> the docs or specification or wherever how to handle such a case?

Not that I have any say in the matter, but having the services directory
in the pc file would clean up a lot of my configure scripts...

Gary Kramlich <grim at>

More information about the dbus mailing list