On Wed, Jun 4, 2014 at 8:21 AM, Tanstaafl <tansta...@libertytrek.org> wrote: > And yes, as devs get lazier (decide to rely on systemd rather than build it > to work independently of the init system), this will in fact result in > *users* (read: those lacking the skills to code every program out there to > work without systemd) eventually being *forced* to switch to systemd. > > That is simply the reality. You can ignore it if you like, but it doesn't > change it. Forced is forced.
Well, if your goal is to persuade people to change, I'd suggest taking that to the upower mailing list, since they're the ones who added the systemd requirement. All anybody at Gentoo did was fork it and provide an alternative. The fiasco was the result of it being unclear that the option existed. However, the general trend I've seen is that when people complain to upstreams that they don't want them to depend on systemd, upstream tends to tell them to go make their own upstream. So, instead they complain on lists that don't ban them, like this one. It doesn't really fix anything though - it just gets everybody upset and often results in misdirected anger. The only thing Samuli did was give non-systemd users a workaround for an upstream problem, and the news clarifying this came out a bit late. I generally intend to switch over to systemd, but I for one would love for there to be the option to use alternatives. Simply wishing that won't make it happen, and since i don't really intend to use the alternatives it is a bit hard to get the motivation to help fork the world. That's just the way the wind seems to be blowing these days. Rich
