On Thu 06 Jul 2017 at 15:49:41 +0200, Erwan David wrote: > There are also packages which add a dependency on systemd whereas the > same software works perfectly on FreeBSD, thus without anything > ressembling it (eg hplip).
hplip does not have systemd as a Depends:, In about 2009 hplip introduced support for policykit. Utilities such as hp-setup could be run as an ordinary user rather than as the superuser. Therefore, Debian's hplip depends on policykit. Sensible, you would have to agree. But, nearly 10 years later, policykit-1 depends on libpam-systemd, which, in turn, depends on systemd. No real problem there; an installation of policykit-1 by hplip does not change PID 1. For an hplip installation not to lead to the installation of systemd the target to aim at is libpam-systemd. Good luck with that, but don't blame hplip; it is only providing a secure environment for users to operate in. > This leads to upgrade from a jessie without systemd will install it. A Jessie hplip pulls in systemd so your point is obscure. Perhaps you could analyse in detail what FreeBSD does with hplip to clarify how it differs. -- Brian.
