Gentoo Archives: gentoo-dev

From: Pacho Ramos <pacho@g.o>
To: release-team@×××××.org
Cc: "gnome@g.o" <gnome@g.o>, gentoo-dev <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] Gnome Stabilization 3.6 or 3.8
Date: Wed, 11 Sep 2013 11:16:14
Message-Id: 1378898158.987.13.camel@localhost
In Reply to: Re: [gentoo-dev] Gnome Stabilization 3.6 or 3.8 by Olav Vitters
1 El mié, 11-09-2013 a las 11:41 +0200, Olav Vitters escribió:
2 [...]
3 > > * We maintain networkmanager and bluetooth support optional, and this
4 > > has been the case since 3.2 iirc even though upstream flat out refuses
5 > > to merge our perfectly fine patches
6 >
7 > Feel free to cc release-team@×××××.org on such patches. I am not saying
8 > something would change, however, Bluetooth is optional in gnome-shell
9 > (though in 3.9.x it crashed if you disabled it). Seems a bit strange to
10 > have it optional in one place, forced in another.
11 >
12
13 Upstream (I think most Bastien) strongly refuses to include that
14 patches, should we send you via mail to release team? (I can try to find
15 the bugs again and CC you there, but you will only see those closed as
16 WONTFIX because we aren't supposed to disable that support (colord,
17 networkmanager, kerberos...)
18
19 [...]
20 > Intention was not to force systemd. It just seems to have ended up that
21 > way. The various times I asked there has been a lot of work going on
22 > into supporting non-systemd configurations as changes are made. However,
23 > that work is mostly untested and likely buggy (things needs to be used).
24 > I thought the work was good enough (though knew that Debian would go
25 > with requiring systemd as a dependency)
26
27 It's "de facto" forced, otherwise, gdm cannot be stopped properly (until
28 cgroups support is not implemented in other RCs alternatives), power
29 management support is lost...
30
31 >
32 > It seems that for Wayland support we somehow do need to require logind
33 > (I forgot why exactly, though I do have IRC logs somewhere). At the
34 > moment that seems unlikely to change. I'm planning to write a proper
35 > message about this to distributor-list.
36
37 Then, it will also need systemd to be running as systemd >= 205 cannot
38 have logind working alone.
39
40 > Most of the development was done within ConsoleKit, now mostly done
41 > within systemd. It would be nice if the logind part was optional like it
42 > was initially, but I don't know if that would still be a no-go for
43 > Gentoo. E.g. does it have to be ConsoleKit, or is a logind also ok? Note
44 > that Ubuntu is going with Qt, so I don't expect them to do much
45 > development on keeping logind separate from systemd.
46
47 Ubuntu people made a huge effort to let logind work with Upstart
48 running, but that will only work for <=204 version.