Gentoo Archives: gentoo-dev

From: Patrick Lauer <patrick@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [RFC] gtk/gtk2/gtk3 USE flag situation
Date: Fri, 27 May 2016 15:56:51
Message-Id: a6db35d2-0195-b6c4-a613-ea0589412383@gentoo.org
In Reply to: [gentoo-dev] [RFC] gtk/gtk2/gtk3 USE flag situation by Mart Raudsepp
1 On 05/27/2016 04:21 PM, Mart Raudsepp wrote:
2 > Hello,
3 >
4 > Despite it being 2016 and gtk2 pretty much dead, buried and forgotten
5 > upstream, many applications still support only gtk2, have subtle issues
6 > with their gtk3 port, or support both, with some of our userbase
7 > clinging to gtk2 for dubious political or aesthetical reasons.
8 >
9 > For the latter cases, despite GNOME teams policy and strong preference
10 > on not providing a choice and just choosing gtk2 or gtk3 (gtk3 if it's
11 > working as good as gtk2), some cases exist where the maintainers want
12 > to provide such choice. In some cases it is understandable for a short
13 > while during transition, e.g firefox. In other cases, it is purely for
14 > the sake of providing the choice of working with a deprecated toolkit,
15 > apparently.
16 >
17 > My highly biased essay aside, we need to finally globally agree on what
18 > we do in this situation. If we allow this choice at all, only for
19 > special cases, or widespread. And if this choice is provided, how do we
20 > name the USE flag.
21 Looking at the gtk-apps I use ...
22
23
24 Firefox with gtk3 is TOFU. UI elements are invisible, Scrollbars are
25 broken, etc.
26 The font rendering is hilariously wrong, even more so than gtk2. I'd
27 call this "late alpha" if I'm in a good mood.
28 ("wrong" ? well, everything else at fontsize ~8-9 is the same as gtk2 at
29 fontsize 24, and gtk3 at ~32. Which means that the defaults are
30 literally unreadable because text ends up 3 pixels high. I have no idea
31 why everything else understands config, and special snowflake has to
32 guess instead...)
33
34 Thunderbird ... oy vey. The new new theme in 45.1 after a new theme in
35 45 repeats all the problems with font rendering, and it's "flat" because
36 who needs to know where UI elements are, where they end, or if they are
37 active/usable. Also fun that *now* it is 'catching up' with the UI
38 stupidity of Android-4, which is abandoned. Change to have change ... :\
39
40 I think Chromium uses their own layer of madness on top of gtk.
41 Chromium-51 has a tiny URL bar which is not resizable (sizing only
42 affects the html viewport). It is proportionally smaller than
43 Chromium-50, so I guess they switched to gtk3 too.
44
45
46 All in all: GTK+-3 looks substantially worse, has wrong font rendering
47 (which gtk2 already got wrong), and I consider it a strict downgrade
48 from gtk2. So where I can, when I can, I will aim to keep gtk2 until I
49 can switch to something that isn't dead upstream or just braindead.
50
51 So while I understand that you don't want to support a toolkit that has
52 no or little support (like qt4, btw, which is abandoned but only about
53 half the things have been ported to qt5) ... as long as it's not at
54 feature-parity some users like me will fight for the option to have
55 usable software. And that means, for now, requiring gtk2 / gtk3 useflags
56 to allow us to choose the correct version where possible. I don't care
57 much how it is exposed, I don't consider "force-gtk2" worse than "gtk2"
58 or "partial-sanity". But it'll take a lot of improvement before you can
59 consider deprecating gtk2, and crude methods like the suggested
60 package.use.mask will motivate me to fix the mistake by reverting it.
61
62 (I remember fighting with ssuominen over guvcview, he always tried to
63 remove the last gtk2 version of it, I readded it because otherwise
64 there's a whole pile of new bad dependencies, he'd remove it again, I
65 readded it, lots of fun. Let's not play that game too much please ...)
66
67
68 Thanks,
69
70 Patrick