Bug#727708: init system other points, and conclusion

[Ian Jackson <ijackson@chiark.greenend.org.uk>]

intrigeri writes ("Bug#727708: init system other points, and conclusion"):
> (Sorry if I am duplicating a point that was already made.
> These threads are huge, and don't fit entirely into my memory.)

That's fine, of course.

> Ian Jackson wrote (30 Dec 2013 18:58:37 GMT) :
> > Unless you are proposing to make systemd mandatory for all Debian
> > installations, this is work that needs to be done anyway.
> 
> "Needs to be done anyway", possibly, but I find it important to make
> it clear that, depending on what decision is made, it affects the
> project as a whole, and many of its members, in very different ways:
> 
> * In one case (upstart is chosen as the default init system), we, as
>   a project, are committed to do this work, at the very least because
>   Policy mandates it, and we want to release without too many
>   RC-buggy packages.

I think you have misunderstood.  Or perhaps I hae misunderstood you.
The "work" that I'm saying needs to be done anyway is the work to
disentange the parts of systemd which are required by (say) GNOME from
the parts which are only relevant for systemd as init.

This is work that would have to be done by the systemd maintainers in
Debian.

> The difference lies in who are the people who "need" to do this work
> "anyway", and who else may instead dedicate their time to other tasks,
> lead by their own desires and needs.

I think that it is right that the costs of undoing systemd's bundling,
be borne by the systemd community (including systemd's advocates and
maintainers in Debian) rather than by Debian (or the rest of the Free
Software world) at large.

Ian.