On Sat, Oct 26, 2013 at 11:07:36AM +0200, Lucas Nussbaum wrote: > I think that there are two different questions: > 1) Could you clarify which init system(s) must be supported by packages > involved during system startup (daemons, etc.) and low-level services? > [ the answer to that question would likely result into a update of > the Debian Policy, section 9.3 and 9.11 ] > [ Note that most daemons will likely still have to support sysvinit > in jessie, in order to handle partial upgrades. ] > 2) sysvinit is currently "Essential: yes", which causes it to be > installed by default by the installer. Should sysvinit stay > Essential? If not, should another init system be Essential? > If not, how should this be addressed in the debian installer? I don't think either of these are the right question. Even if we change the default init system for jessie, because we *must* support backwards compatibility with sysvinit for upgrades, there is no justification for requiring packages to do anything else for jessie and no policy change is needed. Likewise, the Essential: yes bit on the sysvinit package will be in effect for a full release cycle regardless of what init system we choose, so it needs to become a metapackage that depends on an ORed list of possible implementations in order for us to make any change in jessie. The real question before the TC is simply: what should the default init system be for jessie? The rest are technical details that can be straightforwardly worked out once we have a decision on the direction. -- 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