[Pkg-sysvinit-devel] Bug#645540: "Essential" package conflict between sysvinit and systemd-sysv

[Michael Biebl]

Instead of trying to make system(-sysv) Essential, I'm wondering if we
can't just drop the Essential flag from sysvinit.

At least the special semantic property of an Essential package - being
usable directly after unpack - is not relevant for sysvinit afaics.

Being priority: required will also make sure it is installed by default.

Another essential package, like base-files, could depend on sysvinit |
init and systemd-sysv (or upstart for that matter) could add a Provides:
init as soon as we see fit.

This way we would ensure that we always have a working /sbin/init which
basically is what the kernel or the initramfs expects.

What else am I missing?

Cheers,
Michael


As a side note: the upstart package in Ubuntu has dropped the Essential
flag since a very long time.
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 900 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20120206/28ae560b/attachment.pgp>