diff options
| author | Filipe Brandenburger <filbranden@google.com> | 2014-12-23 10:59:14 -0800 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2014-12-25 10:55:42 -0500 |
| commit | 977db91c29083478c6fb7c7bf033e14c567df5d5 (patch) | |
| tree | 5f3a9527d1f73f43228274d1232d5abe1c59f63e /TODO | |
| parent | fa66b606b1a79530bc0d7f70ff30955232e40694 (diff) | |
build-sys: do not use pkgconfig dbus-1.pc to find dbus directories
Do not use the dbus-1.pc pkgconfig settings to determine dbus directories. Use
directories relative to ${sysconfdir} and ${datadir} instead.
This approach was suggested by Simon McVittie in:
http://lists.freedesktop.org/archives/systemd-devel/2014-October/024388.html
Tested by building and installing systemd without the dbus-devel installed.
Without this patch, the dbus files and directories end up in the root of the
filesystem. With this patch, they end up in the same locations as previously
(assuming default ${sysconfdir} and ${datadir}) whether dbus-devel is present
or not. Also made sure that `make check` works without dbus-devel installed.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 2 |
1 files changed, 0 insertions, 2 deletions
@@ -140,8 +140,6 @@ Features: * systemd --user should issue sd_notify() upon reaching basic.target, not on becoming idle -* configure.ac pretends dbus was optional but actually hardcodes use of dbus' pkg-config file to determine various dbus dirs such as policy and activation dirs - * consider showing the unit names during boot up in the status output, not just the unit descriptions * dhcp: do we allow configuring dhcp routes on interfaces that are not the one we got the dhcp info from? |