On Fri, Sep 05, 2014 at 05:05:31PM +0100, Ben Hutchings wrote: > On Fri, 2014-09-05 at 08:47 -0700, Steve Langasek wrote: > > On Fri, Sep 05, 2014 at 10:57:34AM +0200, Josselin Mouette wrote: > > > Noel Torres wrote: > > > > So we are clearly failing to follow the least surprise (for the user) path. > > > > Should not logind depend on systemd-shim | systemd-sysv instead? > > > No. Systemd is the default init system. The default dependencies should > > > reflect that. > > No, the default dependencies should reflect the *principle of least > > surprise*. Installation of logind causing your init system to be changed if > > you have already selected a non-default init system in jessie is failing > > this principle. > > The selection of default init system should be done via the Essential > > packages *only*. > In that case, perhaps the alternate init systems should Recommend > systemd-shim? No, that's not the true package relationship. There's no reason that you should always get this added service by default when you install a system with non-systemd init that doesn't need logind. Making this a recommends would be a workaround for bad metadata in the libpam-systemd package; we should fix that problem at its source the right way. -- 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