From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: GTK USE flag situation (gtk, gtk2, gtk3; relevant to bug #420493)
Date: Wed, 12 Feb 2014 08:23:54 +0100 [thread overview]
Message-ID: <1392189834.18051.10.camel@belkin5> (raw)
In-Reply-To: <52FAC142.3000602@gentoo.org>
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)
next prev parent reply other threads:[~2014-02-12 7:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 22:39 [gentoo-dev] RFC: GTK USE flag situation (gtk, gtk2, gtk3; relevant to bug #420493) Alex Alexander
2014-02-11 23:04 ` Samuli Suominen
2014-02-11 23:51 ` Ulrich Mueller
2014-02-12 0:00 ` Samuli Suominen
2014-02-12 0:20 ` Ulrich Mueller
2014-02-18 9:39 ` Ben de Groot
2014-02-19 17:40 ` Sergey Popov
2014-02-11 23:13 ` Gilles Dartiguelongue
2014-02-12 0:33 ` Chris Reffett
2014-02-12 6:27 ` [gentoo-dev] " Ryan Hill
2014-02-12 7:23 ` Pacho Ramos [this message]
2014-02-12 8:09 ` [gentoo-dev] " Michał Górny
2014-02-12 22:46 ` Chris Reffett
2014-02-12 23:56 ` Gilles Dartiguelongue
2014-02-13 0:22 ` Matt Turner
2014-02-12 8:10 ` Gilles Dartiguelongue
2014-02-13 0:45 ` [gentoo-dev] " Ryan Hill
2014-02-21 3:19 ` [gentoo-dev] " Donnie Berkholz
2014-02-12 7:29 ` Lars Wendler
2014-02-12 8:14 ` Gilles Dartiguelongue
2014-02-12 8:05 ` Michał Górny
2014-02-12 9:14 ` Tom Wijsman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1392189834.18051.10.camel@belkin5 \
--to=pacho@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox