Adding a conflict between systemd-sysv and -shim ?

[Martin Pitt]

Yann Dirson [2014-09-24 23:22 +0200]:
> When one migrates a system from sysvinit-core to systemd-sysv, it
> feels strange to have systemd-shim still installed.  I expected that a
> conflict would get rid of systemd-shim (probably systemd-shim should
> declare the conflict against systemd-sysv).  Is there a reason not to
> have such a conflict ?

Yes, there is. Technically the packages don't conflict at all.
systemd-shim is completely inert when systemd is PID 1. But even with
systemd-sysv installed one may still boot with init= set to sysvinit
or upstart, and then you do need -shim.

Martin
-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)