Making it possible to uninstall initscripts / insserv and facilities

[Petter Reinholdtsen]

[Michael Biebl]
> a/ Pere suggested to turn the Required- dependencies into Should-
> dependencies. This means, as long as initscripts is not installed,
> insserv does not fail, but potentially calculates a wrong ordering.
> This is not fatal for systemd though, as the ordering is not used by
> systemd, only the enabled state is relevant.

Can you explain this bit some more?  What does it mean that the ordering
isn't used by systemd?

> b/ We patch insserv to simply make the facilities provided by
> initscripts a nop iff systemd is active, i.e. add a whitelist for
> facilities which may not exist.
>
> This would only require touching one package, but Pere didn't
> particularly like it. It certainly would be a hack.

The reason I do not like this is that insserv do not know about package
names and only do know about the dependency format and derive everything
from there.  I believe it is a mistake to hardcode script names into
insserv.  I also believe it is a mistake to teach insserv about systemd,
which it know nothing about and do not really care, as it only operates
on files in /etc/init.d/ and create symlinks based on the information in
those files.

Btw, what is the boot ordering for the init.d scripts in the packages in
question when booting using systemd, if the ordering provided by the
initscripts framework is missing?  Is it using a different set of
dependencies with systemd?

-- 
Happy hacking
Petter Reinholdtsen