Re: Devuan

Quoting Steve Litt ([email protected]):

> It's an infinite loop. You keep saying there's an easy way to make
> Debian systemd free.

This is _not_ what I said.

What I said was that someone wishing to maintain a Debian-variant
community with an enforced policy (no-systemd or pretty much anything
else) can do so more easily using less-drastic means, versus the far
greater amount of work entailed in doing so by forking the distribution.

Instructions on http://linuxmafia.com/faq/Debian/openrc-conversion.html 
could easily be packaged as a deb to implement that policy for the 
huge subset of Debian described (everything except NetworkManager,
the large metapackages of four DEs, the GNOME packaging variant of
hplip, and a few miscellaneous apps).  Backfilling the rest would
require more work -- work I'm not interested in doing personally as it
involves software I don't care about.

I used the example of the Aptosid (ex-Sidux) and Siduction repos as a
real world example of policy-enforced Debian-variant communities that
do exactly that sort of thing.

I'm quite surprised that you failed to understand what I wrote, as I
think I was abundantly clear.

The only thing I said was 'easy' was collecting the six shell commands 
my OpenRC page cite, that quickly change any Debian 8 'Jessie' system to
use OpenRC (or any of the three other packaged init systems) and enforce
that choice thereafter.  An additional init-system option, nosh, is also
available via a third-party deb package, as mentioned in the footnotes.

That was 'easy' because I didn't even have to code that; I just copied
and pasted (and tested it to ensure it works as designed).


> I keep mentioning that "solution" could disappear any time: 

By magic?

Sorry, I don't see how some theoretical cabal of Debian Project evil
masterminds could override pin-priority package directives and make competent
Debian sysadmins around the world bow to the Dark Lord or whatever.

Perhaps you could explain in detail how that's going to work.  And then
after you do that, explain why (preferably without strenous overreading
of Red Hat CTO interviews).

Please use small words, because clearly you know a great deal more about
administering a Debian system than I do, and I don't wish to be left
behind.