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 918AB138CEF for ; Wed, 12 Feb 2014 07:24:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9BDEBE0B25; Wed, 12 Feb 2014 07:24:00 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 15ACCE0B24 for ; Wed, 12 Feb 2014 07:23:59 +0000 (UTC) Received: from [192.168.1.33] (249.Red-83-44-128.dynamicIP.rima-tde.net [83.44.128.249]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id 762DF33F844 for ; Wed, 12 Feb 2014 07:23:57 +0000 (UTC) Message-ID: <1392189834.18051.10.camel@belkin5> Subject: Re: [gentoo-dev] RFC: GTK USE flag situation (gtk, gtk2, gtk3; relevant to bug #420493) From: Pacho Ramos To: gentoo-dev@lists.gentoo.org Date: Wed, 12 Feb 2014 08:23:54 +0100 In-Reply-To: <52FAC142.3000602@gentoo.org> References: <20140211223913.GB26141@fury> <1392160421.31609.2.camel@kanae> <52FAC142.3000602@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4 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 Content-Transfer-Encoding: 8bit X-Archives-Salt: 6af4f347-bb9b-4d1d-a42b-4b7eebb2dbeb X-Archives-Hash: e2af8a0123aa8b81a6308f8b290f55da El mar, 11-02-2014 a las 19:33 -0500, Chris Reffett escribió: [...] > This doesn't make sense to me at all. I can't see why slotted > libraries can't just use USE flags to specify what toolkit they're > built against, just like any other package in the tree (so, for > example, a package that needs webkit-gtk built against gtk3 would > depend on webkit-gtk[gtk3] instead of webkit-gtk:3). I'm well aware > that there could be limitations I'm unaware of (maybe the package only > can build one at a time?), but this is how it looks to me. By > switching to versioned gtk flags, this kills two birds with one stone: > it makes it obvious to the end user which version they're trying to > build their package against, and it gets rid of the need for (ab)using > revision numbers to implement slots like that. > At least for webkit-gtk, we would still need to have slots as, otherwise, people wanting gtk2 support wouldn't be able to have webkit2 support at the same time (that is needed by, for example, epiphany and other recent webkitgtk consumers), not sure about other slotted packages for gtk2/3 support (I don't have much time just now to recheck all :S)