Bug#911165: debian-policy: drop requirement to ship sysvinit init script with same name
On Tue, 16 Oct 2018 at 20:31:54 +0200, Andreas Henriksson wrote:
> I'm still leaning towards thinking just dropping this section is
> better than doing a direct translation of it to the current systemd
> reality which might just end up being confusing and help noone.
One part of this section that seems valuable to rescue is:
If you have an LSB (or "sysvinit") init script /etc/init.d/foo, and
systemd unit(s) that are intended to be used instead of the LSB init
script on systemd-booted systems, then the package must either include
foo.service, or mask foo.service.
(This is a consequence of how systemd's backwards compatibility for LSB
init scripts is set up. It's a much simpler and easier requirement than
the wording we used to have about how to make Upstart coexist with LSB
init scripts, but it's still a requirement.)
smcv
Reply to: