Re: [gentoo-dev] www-client/chromium gtk3 support

[Daniel Campbell <zlg@gentoo.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09/09/2015 12:20 AM, Paweł Hajdan, Jr. wrote:
> A user asked for optional gtk3 support in www-client/chromium: 
> <https://bugs.gentoo.org/show_bug.cgi?id=559378>
> 
> However, reading e.g. 
> <https://wiki.gentoo.org/wiki/Project:GNOME/Gnome_Team_Ebuild_Policies
#gtk3>
>
> 
says this:
> 
>> having USE=gtk3 to enable gtk+-3 instead of gtk+-2 support is 
>> forbidden
> 
>> package is an application with support for multiple gtk+,
>> maintainer is free to select whatever slot he desires to support.
>> It is strongly advised to use gtk+-3 if functionality is
>> equivalent. This is to reduce workload of bugs being triggered
>> with one slot but not the other.
> 
> What are your recommendations for the best course of action?
> 
> For stability and maintainability, I'd prefer www-client/chromium
> to use the upstream defaults (gtk+-2 AFAIK) since it's most common,
> tested, and supported configuration. If/when upstream moves to
> gtk+-3, we'd just follow.
> 
> I also understand we have users who are eager to run various 
> configurations, and expect Gentoo to be flexible and allow that.
> Would masking a gtk3 USE flag for www-client/chromium be
> acceptable? Are there any other solutions that might work?
> 
> Paweł
> 
x11-misc/spacefm supports multiple toolkits as well. I stay in line
with GNOME suggestions by making gtk3 the default, but gtk2
configurable via USE. Versioned USE flags are generally frowned upon,
but I see no better way to support both a GTK3 default *and* allow for
the GTK2 support. Part of the reason I came to Gentoo (and became a
dev) is to support user choice, and personally as a maintainer that
matters more than suggestions.

If the GNOME team has a solid recommendation for supporting both GTK2
and 3, I'll read it. But for now, defaulting IUSE to gtk3 and allowing
the user to set gtk2 is the best of both worlds imo.

- -- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJV797CAAoJEAEkDpRQOeFwcl4P+wUAQwjoVCdvEjELYxSpgHZS
I6xd+YOikyRuio68+UB1pBeJpFkZkblQ7DS6loK8eIQFSM+C3RQ1bM2Qa/iQ7he4
4X5NNDVMI8UgT568TsH0d6k/AuUxGuRlH6lrMKOdXZfrCen/pl0QLTtWkI+sOzh4
hAxDKoXf3CntmIrwCp2bsTDyU79uX+X2mQHnjz49U7FXYWc+WDPMaFK1dQzp59wD
vLnMFNoh27gVSWNwsYiy6yo7hL73vIF2ZQaiYnQDKR3nxOLvWLTsCY6JSfebSJiX
bv/dyUldcjK4vaEaES0+PYHVww7A3f13QbC3b3/8oTxAHfMZpYCWnskUN1hCx337
I+/LBR2KrSsoyLPNNfMuVk0t4h2TEQw2SHED4+ObQ2qQ4tc1SmdWPn3g//2e8cFU
Zl2fLxfrXiQxCUB5dByUXSzD1lPCo7BvespewoJ3g+YkeZpxfQ4iyt91otG8sooW
VNJF/+gqgBSGnJPZQBjx1n6bjx08B++pCoybvZGn2NUHvLpYe/rgA3oZyg0clZND
dEbkgXbbn3dJMbiaTzT7ou2Icv0T0F7+xHxq4IFvZ7NgthrNhmTFllWsgC0rpM3/
RLwjFfaekap1utGew5W3+77xyKIxDIeBFGQm0pP7KgQDHn+M6Cs5+r64vljDXsWp
0MYg19z2jBdxbCpaMxET
=Q16B
-----END PGP SIGNATURE-----