Hello,

On Fri, Dec 23, 2016 at 11:18:03AM +0100, Christian Seiler wrote:
> Hi there,
> 
> sorry for the formatting, writing this on my phone.
> 
> 
> Am 23. Dezember 2016 10:18:52 MEZ, schrieb Andreas Henriksson 
> <andr...@fatal.se>:
[...]
> >on upstream issue #2.
> 
> I'm not sure that'll work. In contrast to systemd services init scripts are 
> necessarily very distro-dependent. You can hack together something that's 
> cross-distro, but that's really ugly.
[...]

If only looking at major distributions Debian is likely the only one
still using init scripts. OTOH apparently upstream thinks catering
for the niche distros is important enough to file a bug report
about it against his own software. Making the debian init script
more portable could just be seen as a future improvement IMO. :P

[...]
> IMHO init scripts are distro-dependent anyway (see above). I didn't know 
> about the issues in init-d-script and since I use that in my own packages, 
> I'll look into that. Any pointers?
[...]

See existing bug reports, many contain init-d-script in title at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=sysvinit

My personal opinion is that for example breaking the LSB hooks
that redirects direct /etc/init.d/foo invokations to using systemctl
(which you really, really want to do when) under running systemd is
quite unfortunate (#826214, #826215). I also find it very unfortunate
that minor bugs that goes unfixed gets worked around depending on
implementation-specific ways which means that the more people who use
init-d-script the hard it will become to ever fix it up without breaking
all users which then relies on the exact current/previous
implementation.

I've already asked about rolling back to the old skeleton but
since noone is caring for sysvinit that has just ended up in void.
When this issue was brought up with dh-make maintainers they instead
decided to just completely drop sysvinit example. :/

If needed, we should probably discuss this further elsewhere as this
is getting off-topic for the llmnrd sponsorship bug report.

Regards,
Andreas Henriksson

Reply via email to