> On 29. 8. 2020, at 17:41, Gunnar Wolf <gw...@gwolf.org> wrote: > > The use case for docker-systemctl-replacement is quite legitimate and > common; containers will often not need to support a full-fledged init > system. And given that php-fpm, the package in quesiton, closely fits > the container use case, we feel important to urge the php-fpm > maintainers to work constructively to find a suitable way to describe > the needed dependencies so that php-fpm can be installed in a > containerized system without a full init system.
Gunnar, I understand the tech-ctte position here, and I offered several ways how to get out of this: * src:systemd could have split the systemd-tmpfiles into a separate package (honestly, that would be preferable) * src:docker-systemctl-replacement could add a shim for systemd-tmpfiles and declare “Provides: systemd-tmpfiles” * src:opentmpfiles could have been just a little bit maintained, so it stayed in the testing and it could provide the thin wrappers All these approaches would have helped Debian in a general way, instead the situation is stuck at being php7.4-fpm responsibility. This makes me extremely sad. Ondrej -- Ondřej Surý (He/Him) ond...@sury.org
signature.asc
Description: Message signed with OpenPGP
