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