[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#727708: multiple init systems - formal resolution proposal

On Sat, Feb 01, 2014 at 01:12:34PM -0800, Josh Triplett wrote:
> In particular, in the case of GNOME, I don't see any package in the
> archive yet for a fork of logind that depends on systemd-shim instead of
> systemd, so there's no alternative available for GNOME to depend on.

There is no fork of logind *required* today.

This bug would be fixed, today, by a dependency on 'systemd-shim |
systemd-sysv', which is what I asked for in the bug.

> There's little point to adding a virtual package with no providers yet,
> because until the cloud of uncertainty leading to 727708 gets resolved,
> a (direct or indirect) dependency on "systemd-sysv | empty-alternative"
> seems unlikely to fly, and seems likely to lead to more rants against
> the GNOME maintainers for depending on systemd.

Of course, because that would be forcing a non-default init system (forcing
installation of systemd-sysv before the decision has been taken on the
default init system).  As things stand today, a dependency on systemd-shim |
systemd-sysv would fix the bug for our users without forcing a change of
init system on upgrade.

Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org

Attachment: signature.asc
Description: Digital signature

Reply to: