Bug#727708: multiple init systems - formal resolution proposal
On Mon, Jan 27, 2014 at 08:54:13PM -0500, Michael Gilbert wrote:
> On Mon, Jan 27, 2014 at 11:59 AM, Ian Jackson wrote:
> > 2. Debian intends to support multiple init systems, for the
> > foreseeable future, and so long as their respective communities
> > and code remain healthy. Nothing outside of an init system's
> > implementation may require a specific init system to be pid 1.
>
> I think the push back you're seeing about this is because the second
> sentence imposes a fairly significant constraint on the project.
>
> Say gnome ultimately requires systemd, and something else in the
> meantime happens to be pid 1, that sentence really gets in the way.
> Why not avoid impeding progress and just let gnome do what it needs to
> work the way it wants, which would involve depending on the right
> stuff to make systemd its pid 1?
Claiming that the scope would be limited to GNOME is already factually
incorrect as of today in experimental.
NetworkManager and PolicyKit can be compiled with support for logind, or
with support for ConsoleKit+upower.
In experimental, they do support only logind.
That's an example where such a policy that requires either a non-systemd
logind replacement, or runtime detection of logind and sensible
fallbacks like in gnome-session, has to be in place to secure that
supporting multiple init systems is actually true in practice. [1]
> Best wishes,
> Mike
cu
Adrian
[1] That's ignoring the possibility that a non-systemd logind
replacement with sufficient functionality for all software following
the latest logind features might show up one day - but without such
a policy such a non-systemd logind would not be a prerequisite for
these packages to move from experimental to unstable and testing.
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
Reply to: