1 |
On 05/15/2013 08:41 AM, Fabio Erculiani wrote: |
2 |
> Are we realizing that in order to keep systemd out of our way, we're |
3 |
> currently writing and maintaining drop-in replacements for the |
4 |
> features that systemd is already providing in an actively maintained |
5 |
> state? openrc-settingsd was the first thing that we as Gentoo |
6 |
> developers (Pacho?) had to write in order to merge GNOME 3.6 into our |
7 |
> tree. |
8 |
> |
9 |
> And now that GNOME 3.8 is out, the game starts over again: logind is a |
10 |
> hard requirement, logind is part of systemd, starting logind (which |
11 |
> replaces consolekit) is not that trivial as you may think (and is the |
12 |
> thing I started to work on anyway). |
13 |
> |
14 |
> And if this wasn't enough, it means that if you want GNOME 3.8, you |
15 |
> need to get logind, which may or not may get included in our udev |
16 |
> ebuild and if it won't, it means that you will be forced to use |
17 |
> systemd as device manager if you want GNOME 3.8, which is believe it |
18 |
> or not, the thing that Ubuntu did. |
19 |
> |
20 |
> The problem will only increase in size as the clock moves. |
21 |
> |
22 |
> And (and!) how does all this fit together with eudev? If the idea is |
23 |
> to either put logind in udev (thus, not creating a separate logind |
24 |
> ebuild), it means that eudev is already a dead end for GNOME users, |
25 |
> unless the eudev team is going to provide logind as well. |
26 |
> |
27 |
> I don't want to start a flamewar here, I was the one who called |
28 |
> Lennart software lennartware, but science is science, and a reality |
29 |
> check had to be done: at some near point in the future, our users will |
30 |
> be forced to replace udev/eudev with systemd. Like it. Or not. |
31 |
> |
32 |
> While I successfully use both openrc and systemd, I _do_ think that |
33 |
> (and expect to see) more and more users (and developers) will be |
34 |
> switching to systemd. |
35 |
> Is there anything we can do? Besides "being prepared", I don't think so. |
36 |
> Do we control upstreams? No, sorry. |
37 |
> |
38 |
> So what do we want to do then? Isolate from the rest of the world? |
39 |
> (It's not a sarcastic question). I hope that everybody does their own |
40 |
> reality check. |
41 |
> |
42 |
|
43 |
The solution is to pressure upstreams not to depend on a specific init |
44 |
system in order to function. How many pieces of software depend on SysV, |
45 |
runit, openrc, or upstart? The only ones I can think of are the pieces |
46 |
that are designed specifically for making those init systems easier to |
47 |
administer, not user-facing software like desktop environments. |
48 |
|
49 |
I sincerely believe that each user and distro reserves the right to |
50 |
choose which software to boot the system with, and desktop environments |
51 |
and other user-facing software should not care about which init system |
52 |
it's running on. In the case of GNOME, I think they're going too far by |
53 |
depending on these things. GNOME devs haven't cared much for user |
54 |
responses (especially wrt GTK+ 3.x), so they are likely to continue |
55 |
integration with systemd. They're free to, but we're free to not use it, |
56 |
too. |
57 |
|
58 |
Personally, I will not have systemd on my box(es). I don't agree with |
59 |
its motives, its methods, or its design. I will not use software that |
60 |
depends on it. If the situation gets bad enough, then I may be forced to |
61 |
switch to another OS... that bothers me, to a degree, but as long as |
62 |
it's on my hardware, I have a say. |
63 |
|
64 |
It would not bother me if distros ostracized Lennart and his projects |
65 |
from the free software world, as he approaches free software with a |
66 |
toxic attitude. We wouldn't miss much IMO. |
67 |
|
68 |
As for Gentoo itself, I'm happy as long as choice remains the governing |
69 |
principle. |