1 |
On T, 2014-02-25 at 12:59 -0500, Rich Freeman wrote: |
2 |
> On Tue, Feb 25, 2014 at 12:03 PM, Samuli Suominen <ssuominen@g.o> wrote: |
3 |
> > How does that work for packages eg. libcanberra where USE="gtk3" is required |
4 |
> > to be enabled for eg. GNOME 3.x and other modern GTK+-3.x applications, |
5 |
> > but at the same time user is running Xfce which needs it's older |
6 |
> > GTK+-2.x based library? |
7 |
> > Then setting USE="gtk2 gtk3" to get the best preferred toolkit breaks |
8 |
> > the default |
9 |
> > USE flags of getting Xfce emerged. |
10 |
> > And the plain 'desktop' is supposed to guarantee out-of-box installation |
11 |
> > of Xfce, while |
12 |
> > not dimishing features from other other applications that might use the |
13 |
> > newer libcanberra |
14 |
> > library. |
15 |
> |
16 |
> I might be missing something in your argument. Looking at libcanberra |
17 |
> it has IUSE="+gtk +gtk3" so users are getting both versions by default |
18 |
> already, and that wouldn't change. |
19 |
|
20 |
But for the use case of not wanting gtk3 when the USE flags are defined |
21 |
as the QA team decided, the user would have USE="gtk2 -gtk3" in her |
22 |
global USE flags, overriding any such default anyways. |
23 |
|
24 |
This is why Gnome team policy reserved these USE flags for libraries and |
25 |
theme engine providers, and only as a workaround for manpower issues on |
26 |
splitting it up into separate SLOTs. Note that this is how all binary |
27 |
distributions also do it - separately prefixed packages (our equivalent |
28 |
to SLOTs) - just they don't have the issue of achieving that all at a |
29 |
source build level. |
30 |
|
31 |
> I do appreciate that there is a distinction between providing support |
32 |
> for gtk2/3 and consuming it, and that there may be value in |
33 |
> recognizing that in general. |
34 |
> |
35 |
> If I missed anything you wanted to point out please let me know. My |
36 |
> intent here is to understand your concerns, not dismiss them out of |
37 |
> hand. |