Hi Russ, On 01.12.19 18:16, Russ Allbery wrote: >> https://lists.debian.org/debian-devel/2019/08/msg00278.html > This is a point that Ian's proposal specifically addresses by accepting > the possibility that packages will be installable but not usable on > non-systemd systems in order to avoid these sorts of dependency chains. Right, but the dependency chain is there to make sure the package is usable on systemd systems, i.e. we'd have to accept a regression for the systemd case in order to facilitate the non-systemd case, which is what we don't want, or live with unrelated packages changing people's init system, which we also don't want. It wouldn't be a problem in practice to break that dependency chain, as systemd based installations tend not to be curated on a package-by-package basis, so the packages would be installed there anyway, but we still need a working policy. Until a technical solution to find the runtime dependencies caused by dbus service activation exists, dependencies in the systemd ecosystem will most likely be specified manually by package maintainers, and similar dependency chains will likely pop up more and more. Simon
Attachment:
signature.asc
Description: OpenPGP digital signature