Bug#851747: sysvinit-utils: drop Essential flag
Thorsten Glaser
t.glaser at tarent.de
Fri Jan 31 01:30:23 GMT 2020
On Fri, 31 Jan 2020, Andreas Henriksson wrote:
> > One of mine popped up, and, while I might investigate into
> > writing a systemd service for it,
>
> In my opinion it's just time (well overdue if you ask me) that
> /everything/ gets native systemd units. The sysvinit compatibility is
> just a compatibility shim. It doesn't give you many of the advantages of
> systemd that someone using systemd would expect.
Yesss, but I cannot test them, and I don’t know about the specifics.
> I don't think that's needed as vars.sh (and sysvinit-utils) is
> (and likely always will be) guaranteed to be installed on a
> sysvinit(-core) system.
Wasn’t this thread about the issue of what to do with them
on a non-sysvinit system that uses initscript fallback (and
there are multiple of those)?
> Given that exists, it's not possible for lsb-base to depend on
> sysvinit-utils as it would cause a circular dependency.
Yeah… except if you split the scripts into another package.
bye,
//mirabilos
--
15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)
More information about the Debian-init-diversity
mailing list