On 16/11/17 01:59, Steve Litt wrote:
This situation is nothing unexpected. Many of us predicted in 2014 that Debian would continue throwing down all the anti-anti-systemd obstructionism they could muster. It would not be unreasonable to expect that the time will come where most Debian packages will fail to provide sysvinit scripts.
Or, an alternative, non-conflictual interpretation -- people scratch the itches they have.
If/when this time comes, we have several alternatives: 1) Help the Debian maintainers, as several have suggested in this thread. 2) Write our own sysvinit scripts, for Devuan only. 3) Write Process Supervisor scripts, and run daemons from a Process Supervisor. I personally don't like #1. The Debian maintainers are obstructionists, so I wouldn't help them: I wouldn't give them the sweat off my W*(#RF(#*.
You wouldn't be giving any thing to the Debian developers, you'd be giving to the Debian *users* (and, therefore) to the users of every Debian derived distribution, including Devuan.
#2 is nice, helps give Devuan a unique brand, but IMHO making and maintaining a good-for-all-setups sysvinit script is difficult and time consuming. As a matter of fact, those horrible scripts necessary to cover most cases, is what made people furious at sysvinit in the first place: I don't think anyone cared about boot time or parallel instantiation.
But you are outraged that the some Debian developers don't want to do this, accusing them of bad faith.
_______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
