2 ms·
> Given this, what is the rationale for requiring, as a strict no-you-can't-be-in-Debian-otherwise requirement, Debian Maintainers to provide and write sysvinit
by yjftsjthsd-h 7y ago
> Given this, what is the rationale for requiring, as a strict no-you-can't-be-in-Debian-otherwise requirement, Debian Maintainers to provide and write sysvinit scripts, when only a very small minority is using sysvinit?
Because Debian decided that they want to have the ability to ever support anyting other than systemd. If they lose support for initscripts that are portable across PID 1s then Debian===systemd will be true and it will be extremely hard to ever change it.
- belorn 7y agoOne way to work around that is to either demand a sysvinit script or a systemd service file that can be automatically turned into a sysvinit script by a converter. It would not be pretty but it would allow the 1% without putting unnecessary constraint on the maintainer.