1 |
On Wed, 2015-09-09 at 09:20 +0200, Paweł Hajdan, Jr. wrote: |
2 |
|
3 |
In chromium's case (a new gtk3-based ui that needs wider testing), a |
4 |
local gtk3 USE flag does make sense. |
5 |
|
6 |
But in general, the gnome team recommends avoiding the gtk3 flag |
7 |
whenever possible. We definitely don't want it to become a global flag. |
8 |
We are trying to avoid the following scenario: |
9 |
|
10 |
(1) Dozens of ebuilds add gtk3 USE flag, and the semantics of the gtk3 |
11 |
flag differ wildly in those ebuilds: |
12 |
(a) build an optional gui that happens to be based on gtk3 (instead |
13 |
of no gui at all); |
14 |
(b) build experimental gtk3-based gui (instead of stable gtk2 gui as |
15 |
recommended by upstream); |
16 |
(c) build recommended gtk3-based gui (instead of legacy gtk2-based |
17 |
gui which is not supported by upstream any more); |
18 |
(d) build widget library and utilities for gtk3 (possibly in parallel |
19 |
with gtk2 widgets and utilities); |
20 |
(e) build widget library and utilities for gtk3 (and disable gtk2 |
21 |
widgets and utilities - without making any effort to allow both |
22 |
gtk2 and gtk3 support in parallel by splitting the package or |
23 |
renaming a few files). |
24 |
(3) Since the flag is used all over the place, some users try to |
25 |
globally enable or disable it, depending on their personal feelings |
26 |
about Adwaita's tab shapes. |
27 |
(4) Since the flag sometimes means "build a gui (instead of no gui at |
28 |
all)" at some point it gets globally enabled in some profile. |
29 |
(5) Users are forced to maintain giant lists of package.use entries to |
30 |
get a usable desktop environment. Unhappiness reigns. |
31 |
|
32 |
In other words, to avoid the scenario that happened during gtk1/gtk2 |
33 |
transition, and which is now starting with qt4/qt5 [1]. |
34 |
|
35 |
[1] https://archives.gentoo.org/gentoo-dev/message/11e3d077e0d9c953597c3d17f327c6b3 |