3 ms·
I think the problem can be restated more clearly thus: Today, Debian Packaging Policy requires packages to supply an sysvinit-style init script. In order for
by teddyh 7y ago
I think the problem can be restated more clearly thus:
Today, Debian Packaging Policy requires packages to supply an sysvinit-style init script. In order for a software package to be allowed in Debian, a software package which does not have such a script from the upstream developer(s) must be provided such a script by the packager; the Debian Maintainer.
However, the Debian default init system is systemd, and this seems to be a stable situation. No other init system seems to be gaining more than minuscule traction, and 99% of Debian installations keep using systemd. 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?
One should always remember that all work in Debian, and also frequently upstream development, is provided by volunteers, and very little can be reasonably demanded unless there are very good reasons for doing so.
There are also other ways to more gently push packages to provide sysvinit compatibility. The Packaging Policy could have a SHOULD requirement instead of a MUST (to use the RFC 2119 terminology). There could be a Lintian warning given to packages which does not provide sysvinit scripts matching their systemd service files. I’m sure there are additional ways.
Most software probably already have sysvinit scripts from upstream already. These would not go away. Most of the remaining Debian packages have sysvinit scripts written by the Debian Maintainer, and these would not go away either. The question is what to do with new upstream software which inherently depend on systemd, and the Debian Maintainer does not feel able to write a sysvinit script. Should this software be prohibited from going in Debian?
I think the answer is obviously “no”, when looking at it this way.
But I’m only a Debian Maintainer (and only of my own upstream software), not a full Debian Developer, so what do I know?
- 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.
- JohnFen 7y ago> 99% of Debian installations keep using systemd. Where does this statistic come from? None of my Linux machines report what my installation is or is not using, and I doubt that I'm alone in this.
- teddyh 7y agoIt was cited in the LWN article; the original source is Marco d’Itri: https://lists.debian.org/debian-devel/2019/10/msg00380.html https://lists.debian.org/debian-devel/2019/10/msg00380.html See also the popcon statistics for the systemd-sysv and sysvinit packages: https://qa.debian.org/popcon-graph.php?packages=systemd-sysv+sysvinit-core&show_installed=on&want_percent=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1 https://qa.debian.org/popcon-graph.php?packages=systemd-sysv...
- JohnFen 7y ago> It was cited in the LWN article Yes, I saw that, but it doesn't explain how the figure was arrived at. If it's from popcon, then the figure is very suspect.