| 1 |
On Thu, 20 Feb 2014 11:28:36 +0200 Samuli Suominen wrote: |
| 2 |
|
| 3 |
> |
| 4 |
>On 20/02/14 11:23, Steev Klimaszewski wrote: |
| 5 |
>> On Thu, 2014-02-20 at 03:59 -0500, Alexandre Rostovtsev wrote: |
| 6 |
>>> And this is an example of why everyone on the gnome team doesn't |
| 7 |
>>> like the "gtk3" flag. Because well-meaning developers will be |
| 8 |
>>> looking at their one corner of the portage tree, deciding that they |
| 9 |
>>> are going to handle the choice of gtk version without slotting, and |
| 10 |
>>> not consider the effect on the distro as a whole. |
| 11 |
>>> |
| 12 |
>>> You know what's going to happen now, after the QA team decision? |
| 13 |
>>> |
| 14 |
>>> First of all, lots of developers will start renaming "gtk" to |
| 15 |
>>> "gtk3" in their ebuilds' IUSE. |
| 16 |
>>> |
| 17 |
>>> Which means "gtk gtk3" will soon have to be added to USE in |
| 18 |
>>> targets/desktop/gnome/make.defaults (currently, the gnome profile |
| 19 |
>>> globally only has USE="gtk" because the "gtk3" flag is evil). |
| 20 |
>>> |
| 21 |
>>> And users of non-gnome profiles who use gnome applications will of |
| 22 |
>>> course manually add "gtk gtk3" to USE in their local make.conf. |
| 23 |
>>> |
| 24 |
>>> Unfortunately, at the same time, lots of other developers are going |
| 25 |
>>> to start adding support for building against gtk2 XOR gtk3. Because |
| 26 |
>>> of course "Gentoo is about choice", and the more choices, the |
| 27 |
>>> merrier, and the gtk3 flag has been declared as supported by the QA |
| 28 |
>>> team. And that means lots of REQUIRED_USE="^^ ( gtk gtk3 )". |
| 29 |
>>> |
| 30 |
>>> For the gnome team this results in a headache: maintaining a big |
| 31 |
>>> list of "-gtk" / "-gtk3" entries in |
| 32 |
>>> targets/desktop/gnome/package.use so that gnome users get a |
| 33 |
>>> sensible choice and don't need to edit /etc/portage/* just to |
| 34 |
>>> emerge widely used desktop tools. |
| 35 |
>>> |
| 36 |
>>> But for non-gnome users who manually added USE=gtk3 to make.conf, |
| 37 |
>>> this means regular emerge conflicts after sync, forcing them to |
| 38 |
>>> *guess* whether "-gtk" or "-gtk3" in pacakge.use is the better |
| 39 |
>>> choice. Maybe with portage auto-suggesting the wrong solution just |
| 40 |
>>> to add to the wonderful user experience :/ |
| 41 |
>>> |
| 42 |
>> See, now this is an example of a good email as to why supporting both |
| 43 |
>> can be a hassle for more than just one desktop. Instead of telling |
| 44 |
>> me that I'm dumb for thinking it's a good idea to follow upstream's |
| 45 |
>> supported ideas, and that we should force one or the other. |
| 46 |
>> |
| 47 |
>> The KDE team seems to be able to deal with it just fine, but somehow |
| 48 |
>> it's impossible and hard for the GNOME team. Why is that? What does |
| 49 |
>> KDE do differently that makes it feasible? |
| 50 |
>> |
| 51 |
>> |
| 52 |
> |
| 53 |
>No, they didn't manage it, at all, which why we don't see Qt3/KDE3 in |
| 54 |
>tree anymore. |
| 55 |
> |
| 56 |
|
| 57 |
Very bad excuse... They punted kde3 because they didn't have the |
| 58 |
manpower to stem both KDEs... |
| 59 |
|
| 60 |
-- |
| 61 |
Lars Wendler |
| 62 |
Gentoo package maintainer |
| 63 |
GPG: 4DD8 C47C CDFA 5295 E1A6 3FC8 F696 74AB 981C A6FC |
Archives