From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 3F05913828B for ; Fri, 27 May 2016 18:23:29 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D9F2C23400C; Fri, 27 May 2016 18:23:21 +0000 (UTC) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 87C5521C012 for ; Fri, 27 May 2016 18:23:20 +0000 (UTC) Received: from [192.168.6.147] ([91.125.237.217]) by mrelayeu.kundenserver.de (mreue104) with ESMTPSA (Nemesis) id 0MG9cl-1bLVdh1AbX-00FAe7 for ; Fri, 27 May 2016 20:23:18 +0200 Message-ID: <5748908F.5000706@iee.org> Date: Fri, 27 May 2016 19:23:11 +0100 From: "M. J. Everitt" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] gtk/gtk2/gtk3 USE flag situation References: <1464358866.13834.59.camel@gentoo.org> <20160527154051.GA9431@whubbs1.gaikai.biz> In-Reply-To: <20160527154051.GA9431@whubbs1.gaikai.biz> X-Enigmail-Version: 1.6 OpenPGP: id=93C22371 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="JKTuW3iBuMhQEfICS9lvoGxAKbs5ljol7" X-Provags-ID: V03:K0:GV9u5t0kGRKMpUhwn/PngDGOIRURvKMlOLDesEmARAxzEfoMQNC lKY/QkAEcy5rNU9elreJK0Sp6hM+iZuGHg2TswYuauyoWA6kiT1ktciZF+oKuXC86arqmc7 KNznZLUvHIvtJlsKqzhlJMedS1xs8hW4uK/Xe8Y/0I0eTbVmOhZqAdM3c3SHCwhWMA91gLU DBgJ8X7nPzWFe+rKuoJIw== X-UI-Out-Filterresults: notjunk:1;V01:K0:/7ziHX2/D+o=:NgDMq3yJNkLLqESBpzupJd RAgbjejrn2+SNQas2xCtjC7XlpnWNozgUBAnuKHx35mfxLsv5D4sMgPohAIoEf3UzQrxzfS9+ mKEVUsG6nB4kn3A2bJbwJxiE+ACAoITUnKBS7YpPow8GjtDTFeKSyZWvhUEu0l/Wd/wl8Bvlq SScVPz42J+I/B/3djAfg76XA/GDvYHC85APmocgjAzinDdYw5g2RNX0dHU/B+2+1KNP/Y/oaG 88fRBhYYugiz/Q4cXYX9RZydzI2hOkV8KTLn3xrvSfM5kAssLRz4DXt/zE+7UlX1t3uBJi/kL Bjh1Bj6kzixpvzCHRcLlJKFXKxlUzuzKsq62m/cFV+232GMq9X0Udx6fGFPqDqeFzuzFELAvG PbO2LWorSvJ4I3EM1ssYsF8hX18g9TPhBbE4K6G1xjzx/EBElgnT+y4MTjA56Dd32k/Qqwnct XMZ76THIS9ermrU8Mbs55mAw+Sh7F+U/TxNTxclpq+zla4f1tE1qQ40uWNs1FkazgGf3hzLYQ dj5Pu2f9/TIA1VloxQsiPgM9mrdWgecH3AbeOeMjGOqKEb2i3crl/vJIURSAI8EVKcWUSfluz iNmTSfqPNIInSlOw7tDqrqb/s2e6fyNzhcoiDpYg8iWzpFukQNaoWyoAI5UnvJ6TL+csDAWmu vTRLWtH65MKyhQUg6fx1hr21Q9VQ8PfVpYoPrTq/ZL3tt1BKOznMjAkm6qWHOpV2RGO8= X-Archives-Salt: 25867169-c82b-4536-a6e5-10dada94bd55 X-Archives-Hash: 8252401360253b11279c33f73fd9e8b6 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JKTuW3iBuMhQEfICS9lvoGxAKbs5ljol7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 27/05/16 16:40, William Hubbs wrote: > On Fri, May 27, 2016 at 05:21:06PM +0300, Mart Raudsepp wrote: >> Hello, >> >> Despite it being 2016 and gtk2 pretty much dead, buried and forgotten >> upstream, many applications still support only gtk2, have subtle issue= s >> with their gtk3 port, or support both, with some of our userbase >> clinging to gtk2 for dubious political or aesthetical reasons. >> >> For the latter cases, despite GNOME teams policy and strong preference= >> on not providing a choice and just choosing gtk2 or gtk3 (gtk3 if it's= >> working as good as gtk2), some cases exist where the maintainers want >> to provide such choice. In some cases it is understandable for a short= >> while during transition, e.g firefox. In other cases, it is purely for= >> the sake of providing the choice of working with a deprecated toolkit,= >> apparently. >> >> My highly biased essay aside, we need to finally globally agree on wha= t >> we do in this situation. If we allow this choice at all, only for >> special cases, or widespread. And if this choice is provided, how do w= e >> name the USE flag. > (qa hat in place) > > There is a qa policy about this. All packages in the tree should > move away from the non-versioned gtk use flag to versioned use flags, > like the ones the qt team uses [1] [2]. > > This seems to be the best compromise. It allows the maintainers of the > packages to decide which toolkit they want to support. If there is too > much work involved in maintaining a package with dual support, don't do= > the work, just make it support the appropriate toolkit version. > > I have not seen any reason why something like this couldn't work. After= > all, it seems to work for the qt team. > > William > > [1] > https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Policies#gtk.2Fg= tk2.2Fgtk3_USE_flag_situation > [2] > https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Meeting_Summarie= s#GTK_flag_situation Having read the QA policies, surely the route forwards is fairly obvious thus:- - gtk is deprecated and discouraged for any new ebuilds - we add a QA check to repoman to ensure that the 'gtk' use flag is not used in any new ebuilds - existing packages using 'gtk' will get updated to use 'gtk2' or 'gkt3' in the normal cycle Any edge cases here, or is this something that could be workable? MJE --JKTuW3iBuMhQEfICS9lvoGxAKbs5ljol7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJXSJCQAAoJEEwwM0+TwiNxExQP/RWPTA3eq8ykwZiVIS5JgDmv GdlD+n9WDLJJZOGt/S3hHD5KncS3SgKb9XhAKNWcCuN6KSc7qqrdD9pyqPAVSJvt DZXGHJafB8APJ7lG+Rln1Q9/zGlueZm1wOIpVTMKaDvelJSXyKxXczsX/kBWkEc+ MZkT4/3EcyfK4/sPN1Xhn9EpCz1QXQFEys0W1MsgldxYcsIkjexHBLsMRIY4tpQ6 xtB3bbP6Gy09puKEdnpL8dyAr7oXUHpqkK13tjkeOswg4jiRqwAiYOV/3Xug6HNM HVbJy8WPg/69OQSTNeODgWw0fk1WYqrke8bfeLtgr7poezD1qusNyPRz1Vb8Wzes 3gp2xCtP/zslnOGWhdR3XxywGz5yFFFgIe58ipvD+1EUfe3aC8I0Tr8XerDB4dL2 CwLPd8uMoNsEbPaCsOrwp5+ff+NKM1/zFG4DY3LZ4tCcabGt7/UHte4BWsW4j4li S3V5u93il5MVSFJ0yV/fvPsI7AJgW8F5VvfZZ8WDIAlTTuCcLe/ERriMyblg67V1 J4ZXiJScFVXzRgDu8RgFLoFbbUMeYpTU9m4wlJ5ybgPWcABlj5HawiTObfnEuz+L r8HTgh5+iebYKMtN401PKEW3Ddbm7EtHxcBPKDui6XXEJySFLC9eNpjAKoJfHRcK B1QE2oicZM2O2VJDAUk5 =lKcQ -----END PGP SIGNATURE----- --JKTuW3iBuMhQEfICS9lvoGxAKbs5ljol7--