Bug#975075: tech-ctte: Should maintainers be able to block init compatibility changes?
❦ 19 novembre 2020 09:04 GMT, Matthew Vernon:
> 3) many upstreams (esp. those who support BSD) ship a sysvinit file,
> again making the daemon (source at least) package the natural place to
> keep it.
I don't think this is very common. Init scripts are very specific to a
distribution. A Debian init script cannot be used for Redhat. A SUSE
init script does not work with Redhat. I find doubtful that the
compatibility would be better with the BSD init scripts (this may not be
what you meaned). AFAIK, OpenBSD does not use initscripts. A FreeBSD
initscript is unlikely to work on any Linux as it sources /etc/rc.subr.
>From my experience, when upstream ships an init script, this is usually
unsable by most distributions (not to the standard), so it has to be
rewritten. Init scripts are not contributed upstream as upstream doesn't
want to handle all this complexity.
This is in contrast with systemd service files, which are more likely to
work on various Linux distributions.
--
Make the coupling between modules visible.
- The Elements of Programming Style (Kernighan & Plauger)
Reply to: