On Sat, 20 Aug 2022 at 13:51, Santiago Vila <sanv...@unex.es> wrote: > > El 20/8/22 a las 14:40, Santiago Vila escribió: > > So I wonder if reversing the dependency created by debhelper: > > > > systemd | systemd-tmpfiles > > > > would improve this state of things. > > Sorry, the above is confusing. I mean reversing the *order*, so that it > becomes this: > > systemd-tmpfiles | systemd > > The issue here is that those who don't have systemd already installed > (either chroots, non-Linux architectures, or containers) will probably > consider undesirable that systemd is now installed on upgrades. > > Thanks.
I think we do want the default implementation to be pulled in by default, this has already been discussed last time. The standalone packages are not the default, are way less tested, and are simply provided for compatibility for !systemd installations, which again are not the default. There's nothing wrong with having the binary systemd package installed in a chroot - if one doesn't want it, they just have to specify they want the -standalone variant and things will work out just fine. This is not really any different than any other defaults, e.g. if you want dbus-broker instead of dbus-daemon you'll have to manually specify it, as the default is dbus-daemon and that's what gets pulled in if there's no other hint. Kind regards, Luca Boccassi
