dbus/bus/tmpfiles.d
Simon McVittie 54f9aa554a bus: Don't create /run/dbus/containers if the feature is disabled
The `Containers1` interface is not stable or production-ready, and is
compile-time-optional behind a build option, which in fact currently
cannot be enabled (it intentionally provokes a compiler `#error` if
enabled). If it isn't enabled, this directory won't be useful, so
there's no reason to create it.

As discussed in <https://github.com/systemd/mkosi/issues/3189>, if we
use the `@DBUS_USER@` here, it makes `tmpfiles.d/dbus.conf` dependent
on having created the `@DBUS_USER@` via `sysusers.d` or some
appropriate distro-specific mechanism. This is problematic in distros
that split up the functionality of dbus into several layers, such as
Debian: the `@DBUS_USER@` conceptually belongs to the same layer as
the well-known system bus, but `/etc/machine-id` and
`/var/lib/dbus/machine-id` are also used by the well-known session bus,
which is orthogonal to the system bus; so we want `dbus.conf` to be in a
lower layer than the `@DBUS_USER@`.

Signed-off-by: Simon McVittie <smcv@collabora.com>
2024-11-18 19:00:26 +00:00
..
dbus-containers.conf.in bus: Don't create /run/dbus/containers if the feature is disabled 2024-11-18 19:00:26 +00:00
dbus.conf.in bus: Don't create /run/dbus/containers if the feature is disabled 2024-11-18 19:00:26 +00:00
meson.build bus: Don't create /run/dbus/containers if the feature is disabled 2024-11-18 19:00:26 +00:00