Luca, [Sorry for the slow reply, your response was not sent to me.]
On Mon, Jul 25, 2022 at 04:52:32PM +0100, Luca Boccassi wrote: > Indeed it would be wrong. Also the justification doesn't seem correct: > simply installing the 'systemd' binary does NOT switch the init system, > so it's difficult to see how it could 'significant problems' in and by > itself. I know that the original intention was to allow installation of the systemd binary independently of switching the init system. Whilst, in theory, that is still the case, in many, perhaps most real-world situations, installation of systemd does force a change of init. This is because the two available logind implementations (and therefore their dependency chains: libpam-systemd->systemd or libpam-elogind->elogind) conflict and libpam-systemd depends on systemd-sysv. So, when installing just the systemd binary on a system which uses a non-systemd init and the libpam-elogind logind implementation, APT has to change to libpam-systemd which pulls in systemd-sysv and forces the init switch. Logind dependencies are now very widespread. With packages such as openssh-server having a Recommends for it, even relatively minimal server installations will often require a logind implementation. I hope that explanation is clear and helps. Best wishes Mark
