Hi Paul, On Fri, Oct 25, 2013 at 02:43:44PM -0400, Paul Tagliamonte wrote: > And, since I've been informed that this was basically a contentless bug, > I'd like to frame the technical half of the question better: Thanks for bringing this question to the Technical Committee. It's been on my todo list to raise this myself, with the intent of getting a TC decision before the end of this year. With only two months left in the year, it's well past time that we start on this, so thanks for beating me to it. In keeping with discussions I've had with other members of the TC regarding what they feel would help with their decision making process, I've begun preparing a wiki page outlining the position of the upstart maintainers on why Debian should adopt upstart as the default init system for jessie. https://wiki.debian.org/Debate/initsystem/upstart The page is not yet complete - in particular, I'm still fleshing out the "why upstart and not systemd" section. But there's enough there to give the TC a starting point for discussion, I think. > Whereas: > * the init system / pid 1 is a bit of software that multiple packages > provide > * the choice of init system also dictates which types of init scripts > package maintainers write and maintain > * the situation in which packages depend on a feature of systemd that's > not dependent on pid 1 being systemd (such as dbus shutdown, or using > logind) being run without systemd as pid1 is *not* something the > systemd maintainers will support (fairly) is getting *more* common, and > has been introduced into a major package (GNOME) > It is requested that the tech-ctte make a decision as to the init system > Debian shall use as the default, and make a judgement call on where the > efforts to resolve this situation shall go (patching *around* the lack > of systemd, or patching software to use systemd) > I believe this is within the ctte's jurisdiction, given 6.1 section 2. It seems to me that these are two separate questions, one dependent on the other. First we need to decide what jessie will use as the default init system. Once that's decided, if the decision is /not/ to use systemd, we can look at making recommendations about how to approach upstream incompatibilities; but while we should be aware that choosing a non-systemd default does imply a certain amount of work, we shouldn't rathole on deciding how to structure that work if we haven't even decided yet if that work will be necessary. -- 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