From 21e4ad92b2a55b0568b8bfbe35f032b6e91f1331 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Fri, 3 Jan 2014 20:11:18 +0000 Subject: [PATCH] 727708: my draft resolution: steal and edit some words from Russ in para 1,2 --- 727708_initsystem/draft-resolution-iwj.txt | 22 ++++++++++++++++------ 1 file changed, 16 insertions(+), 6 deletions(-) diff --git a/727708_initsystem/draft-resolution-iwj.txt b/727708_initsystem/draft-resolution-iwj.txt index 99378f2..346ca21 100644 --- a/727708_initsystem/draft-resolution-iwj.txt +++ b/727708_initsystem/draft-resolution-iwj.txt @@ -7,12 +7,22 @@ Rubric: Choice of init system: -1. The default init(1) in jessie will be upstart. - -2. Architectures which do not currently support upstart should try to - port it. If this is not achieved in time, those architectures may - continue to use sysvinit. [ Non-use of upstart should not be a - criterion for architecture qualification status in jessie. ] +1. The default init(1) in jessie for Linux architectures will be + upstart. + +2. The default init(1) in jessie for non-Linux ports will be upstart + if it has been ported and confirmed by the porters to be working by + the time of the jessie release. Failing this, the default init(1) + in jessie for non-Linux ports is left to the discretion of the + maintainers of that port. + + [ However, the Technical Committee requests that, should upstart be + unavailable on both Hurd and kFreeBSD, the Hurd and kFreeBSD + porters agree on a single alternative init(1) implementation that + will be shared by both ports. ] + + [ Non-use of upstart should not be a criterion for architecture + qualification status in jessie. ] 3. At least in jessie, unless a satisfactory compatibility approach is developed and deployed (see paragraph 10), packages must continue -- 2.39.5