3 The default init system decision is limited to selecting a default
4 initsystem for jessie. We expect that Debian will continue to
5 support multiple init systems for the foreseeable future; we
6 continue to welcome contributions of support for all init systems.
10 Therefore, for jessie and later releases, we exercise our power to
11 set technical policy (Constitution 6.1.1):
15 In general, software may not require a specific init system to be
16 pid 1. The exceptions to this are as follows:
18 * alternative init system implementations
19 * special-use packages such as managers for init systems
20 * cooperating groups of packages intended for use with specific init
23 provided that these are not themselves required by other software
24 whose main purpose is not the operation of a specific init system.
26 Degraded operation with some init systems is tolerable, so long as
27 the degradation is no worse than what the Debian project would
28 consider a tolerable (non-RC) bug even if it were affecting all
29 users. So the lack of support for a particular init system does not
30 excuse a bug nor reduce its severity; but conversely, nor is a bug
31 more serious simply because it is an incompatibility of some software
32 with some init system(s).
34 Maintainers are encouraged to accept technically sound patches
35 to enable improved interoperation with various init systems.
39 If the project passes (before the release of jessie) by a General
40 Resolution, a "position statement about issues of the day", on the
41 subject of init systems, the views expressed in that position
42 statement entirely replace the substance of this TC resolution; the
43 TC hereby adopts any such position statement as its own decision.
45 Such a position statement could, for example, use these words:
47 The Project requests (as a position statement under s4.1.5 of the
48 Constitution) that the TC reconsider, and requests that the TC
49 would instead decide as follows: