Bug#727708: init system coupling etc.

2014-02-19 Thread Steve Langasek
On Wed, Feb 19, 2014 at 09:37:50AM -0700, Bdale Garbee wrote: Ian Jackson ijack...@chiark.greenend.org.uk writes: I'm going to try to go through this thread and produce a draft Call for Votes based on the proposals, amendments etc. which have been emailed so far. That would be good,

Bug#727708: init system coupling etc.

2014-02-19 Thread Russ Allbery
Ian Jackson ijack...@chiark.greenend.org.uk writes: I think we should probably take that as you proposing and accepting an amendment to your formal proposal. I'm going to prepare the draft CFV on that basis. But it would really help to be more explicit. Right, I know, I wasn't expecting

Bug#727708: init system coupling etc.

2014-02-19 Thread Ian Jackson
Andreas Barth writes (Re: Bug#727708: init system coupling etc.): * Russ Allbery (r...@debian.org) [140212 19:00]: Packages should normally support the default Linux init system. There I would drop the word Linux here - Packages should support our default init systems. For the

Bug#727708: init system coupling etc.

2014-02-19 Thread Russ Allbery
Andreas Barth a...@ayous.org writes: * Russ Allbery (r...@debian.org) [140214 04:36]: That's a much stronger statement than we've made about support for the non-Linux ports in the past, where they're treated at most like another release architecture, which means that packages that have never

Bug#727708: init system coupling draft CFV

2014-02-19 Thread Ian Jackson
Here are the options which have been proposed so far, with the proposed amendments incorporated as applicable. You can find the history (with messageids) in the tc git repo. There are curently four options: Ian mark 2 (inclues amendments from Colin and Ian) Keith Russ (includes one thing

Bug#727708: init system coupling etc.

2014-02-19 Thread Ian Jackson
Steve Langasek writes (Bug#727708: init system coupling etc.): On Wed, Feb 19, 2014 at 09:37:50AM -0700, Bdale Garbee wrote: That would be good, since I at least have sort of lost track of what you think the ballot options will be at this point. Likewise, I've lost the thread of what has

Bug#727708: init system coupling etc.

2014-02-19 Thread Colin Watson
On Thu, Feb 13, 2014 at 06:51:13PM +, Ian Jackson wrote: In the spirit of my response to Noah Meyerhans: In general, software may not require a specific init system to be pid 1. The exceptions to this are as follows: * alternative init system implementations *

Bug#727708: init system coupling etc.

2014-02-19 Thread Ian Jackson
Colin Watson writes (Bug#727708: init system coupling etc.): On Thu, Feb 13, 2014 at 06:51:13PM +, Ian Jackson wrote: Is this a clearer line to draw ? This is largely clearer, thank you, but I find myself tripping over the repetition of tolerable - it looks tautologous to me until about

Bug#727708: init system coupling etc.

2014-02-19 Thread Colin Watson
On Thu, Feb 20, 2014 at 01:31:02AM +, Ian Jackson wrote: I think this is a useful clarification and I accept this amendment. Colin, since you already have it to hand in git I see, could you commit it directly there to the same file ? Sure, thanks - done. -- Colin Watson

Bug#727708: init system coupling etc.

2014-02-19 Thread Russ Allbery
Colin Watson cjwat...@debian.org writes: What I mean by this is that software (with all the exceptions above) may not be shipped in a configuration where you can only use it with certain init systems. For service startup, that just means shipping sysvinit scripts. For other interfaces, that

Bug#727708: [mjr.org] Re: Bug#727708: [gmail.com] Re: Bug#727708: call for votes on default Linux init system for jessie

2014-02-19 Thread Tony Thedford
It is just as I thought.. incompetence has taken control. Good luck with that. On 02/19/2014 08:30 AM, Paul Hedderly wrote: On Wed, Feb 19, 2014 at 01:51:56AM -0600, Tony Thedford wrote: On 02/18/2014 09:34 PM, Jason Frothingham wrote: ... Adopting systemd does not, in any way