Am 09.02.22 um 10:40 schrieb Michael Biebl:
That said, debootstrap ttbomk does not respect Recommends, which is probably why you ended up without dbus.

In d-i, this is solved by having a "standard task", which installs all packages with prio standard (and the priority of dbus was bumped to standard accordingly.)

If you want to intall debian manually via debootstrap my recommendation thus is to install all the packages from the standard task
https://wiki.debian.org/tasksel#A.22standard.22_task
This will get you an installation that is closer to what d-i would create.

The reason why dbus is only a recommends in systemd is that we want to allow for more minimal installations (like in containers, single user servers) where logind is not strictly necessary.

There is some more background at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758111

Now, we could obviously make dbus a hard dependency of systemd, but I'm sure that would equally make some uses unhappy.

The core systemd functionality works fine without dbus installed.
It's additional functionality, like logind ( which among others also handles power button events), unprivileged access by non-root users etc, which we need dbus for.

By using prio=standard and a Recommends in systemd, we provide more flexibility in how the base system can be assembled.

Maybe we are at a point though, where we should just bite the bullet and make dbus a dependency of systemd.

I'd like more input on this matter from other team members though.

I've also CCed Simon as maintainer of dbus, if we'd be ok with this.

Michael

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to