1 |
On 20/02/14 18:27, Tom Wijsman wrote: |
2 |
> On Thu, 20 Feb 2014 11:26:18 +0200 |
3 |
> Samuli Suominen <ssuominen@g.o> wrote: |
4 |
> |
5 |
>> On 20/02/14 10:47, Steev Klimaszewski wrote: |
6 |
>>> On Thu, 2014-02-20 at 10:40 +0200, Samuli Suominen wrote: |
7 |
>>>> On 20/02/14 09:44, Steev Klimaszewski wrote: |
8 |
>>>>> On Thu, 2014-02-20 at 07:55 +0200, Samuli Suominen wrote: |
9 |
>>>>>> On 20/02/14 00:23, Ulrich Mueller wrote: |
10 |
>>>>>>> Following up to today's QA meeting: The gtk3 USE flag is used by |
11 |
>>>>>>> 27 packages, so I suggest making it a global flag: |
12 |
>>>>>>> |
13 |
>>>>>>> gtk3 - Add support for x11-libs/gtk+ (The GIMP Toolkit) version |
14 |
>>>>>>> 3 |
15 |
>>>>>>> |
16 |
>>>>>>> Ulrich |
17 |
>>>>>> that would suggest it's fine to use, and is anything but |
18 |
>>>>>> temporary |
19 |
>>>>>> |
20 |
>>>>>> -1 from here |
21 |
>>>>>> |
22 |
>>>>> MATE desktop (which I hope to bring in to Portage soon) can be |
23 |
>>>>> built against gtk+ 2 or gtk+ 3, and upstream supports doing both, |
24 |
>>>>> so +1 from me. Just because gtk+ 3 is the latest, does not mean |
25 |
>>>>> it's the greatest, and I really wish people would realize that |
26 |
>>>>> newest != bestest. |
27 |
>>>>> |
28 |
>>>>> |
29 |
>>>> Then you pick whatever is best supported for MATE, and ship it |
30 |
>>>> using that. Later when they have completed their support for |
31 |
>>>> GTK+-3, and it's the best supported, you ship that. It's not |
32 |
>>>> rocket science. |
33 |
>>>> |
34 |
>>> OR, since I'm the maintainer, I decide that I'm willing to deal with |
35 |
>>> both, instead of you telling me that I need to pick one or the |
36 |
>>> other. Upstream says both are supported and viable, and I'm willing |
37 |
>>> to deal with the headaches. Just because you're unwilling doesn't |
38 |
>>> mean others aren't. kthx. |
39 |
>>> |
40 |
>>> |
41 |
>> Bye bye distribution level consistency :-( |
42 |
>> |
43 |
>> It's sad that few stubborn developers can do that. |
44 |
>> |
45 |
>> - Samuli |
46 |
>> |
47 |
> "'Ey! Have you heard about it. Gentoo doesn't provide X with support |
48 |
> for Y, then what are their USE flags even for; what a shame, ..." |
49 |
> |
50 |
> If people want to support and use multiple things, let them do so. It is |
51 |
> pretty much what Gentoo and its philosophy are about; which somewhat |
52 |
> can be summarized as providing choices such that we fit the users' |
53 |
> need, and not force our one true way upon them... |
54 |
> |
55 |
> Greetings from someone who runs GNOME 3 and MATE simultaneously; you can |
56 |
> intentionally break it, but why would you? It takes away our happiness. |
57 |
> On the other hand, there's the part where you want to break it for a |
58 |
> reason, perhaps for your happiness; but then I'd like to hear why. |
59 |
> |
60 |
|
61 |
So, no more setting USE="gtk" and assuming the best packaged software |
62 |
will be get installed, |
63 |
be it with what version of the toolkit, 1, 2 or 3 |
64 |
Instead, now you have to selectively do the maintainers job for figuring |
65 |
out which one |
66 |
is the best supported one |
67 |
Despite already picking up a modern theme with both GTK+ 2.x and GTK+ |
68 |
3.x looks, now you |
69 |
might end up with half-crippled software just because some stubborn |
70 |
people choose the |
71 |
looks, not the functionality, to be their motivation |
72 |
|
73 |
Such people really don't deserve to own a packager status if they can't |
74 |
take the time to |
75 |
determine / examine the package's best supported graphical toolkit |
76 |
If multiple ones with similar feature set is supported, then the latest |
77 |
toolkit is preferred |
78 |
|
79 |
But seems like I'm repeating common sense which the GNOME guideline |
80 |
layed out long ago |
81 |
Bunch of new QA developers shoudn't have any power to override that |