From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is Gentoo wiping out Gtk 2 support from packages that support it?
Date: Sat, 09 Jul 2011 09:26:55 +0200 [thread overview]
Message-ID: <4368337.24pI982QGQ@nazgul> (raw)
In-Reply-To: <ACF80033-EB76-4F25-8FB0-BE13A226281C@stellar.eclipse.co.uk>
On Friday 08 July 2011 18:39:04 Stroller did opine thusly:
> On 8 July 2011, at 16:19, Alan McKinnon wrote:
> > ...
> > easy.
> >
> > Two USE flags: gtk2 and gtk3
> >
> > in ebuild:
> >
> > DEPEND="
> >
> > gtk2? (x11-libs/gtk+:2)
> > gtk3? (x11-libs/gtk+:3)
> >
> > "
> >
> > in src-configure() write the code such that it establishes a
> > precedence
> >
> > If both flags are set, build against gtk+:3
> > If only one flag is set, build against that toolkit
> > If no flags are set, do something appropriate.
>
> This is the way it was done for gtk vs. gtk2, but the bug has been
> updated since I first read it (over 24 hours ago) and apparently
> the Gnome team don't want the two separate flags in the future.
>
> I'm not really a gtk or Gnome (or X11) user, so I don't really know,
> but the two separate flags did strike me as a bit of an ugly /
> clumsy way of doing things.
It's also the only mechanism I know of to do it.
If the ebuild will support two toolkits and the choice of which to use
is based solely on a user's preference, there is only one way to
resolve that - a precedence list. There's no way around that.
Some global mechanism would be nice and could be useful in various
cases:
gtk+-2 vs gtk+-3
openssl vs gnuts
mysql vs mariadb
Those are also virtuals.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-07-09 8:11 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 16:35 [gentoo-user] Is Gentoo wiping out Gtk 2 support from packages that support it? Nikos Chantziaras
2011-07-06 17:23 ` pk
2011-07-06 19:37 ` Alan McKinnon
2011-07-06 20:02 ` pk
2011-07-06 20:41 ` Alan McKinnon
2011-07-06 22:53 ` Volker Armin Hemmann
2011-07-06 23:06 ` Dale
2011-07-06 23:20 ` Peter Humphrey
2011-07-06 23:21 ` [gentoo-user] " Nikos Chantziaras
2011-07-07 3:04 ` Dale
2011-07-07 17:42 ` [gentoo-user] " Michael Orlitzky
2011-07-07 19:36 ` Alan McKinnon
2011-07-07 20:01 ` Michael Orlitzky
2011-07-07 20:47 ` Dale
2011-07-07 20:57 ` Peter Humphrey
2011-07-07 21:03 ` Dale
2011-07-08 4:42 ` 微菜
2011-07-06 18:02 ` Volker Armin Hemmann
2011-07-07 2:12 ` 微菜
2011-07-07 2:45 ` [gentoo-user] " Nikos Chantziaras
2011-07-07 3:31 ` 微菜
2011-07-07 7:30 ` [gentoo-user] " Alan McKinnon
2011-07-07 12:07 ` Stroller
2011-07-07 22:50 ` [gentoo-user] " walt
2011-07-07 23:40 ` Neil Bothwick
2011-07-07 16:44 ` [gentoo-user] " pk
2011-07-07 17:14 ` Mark Knecht
2011-07-07 23:52 ` [gentoo-user] " Nikos Chantziaras
2011-07-08 12:11 ` [gentoo-user] " Stroller
2011-07-08 13:14 ` Albert Hopkins
2011-07-08 15:19 ` Alan McKinnon
2011-07-08 17:39 ` Stroller
2011-07-09 7:26 ` Alan McKinnon [this message]
2011-07-09 14:02 ` [gentoo-user] " Nikos Chantziaras
2011-07-08 17:50 ` Nikos Chantziaras
2011-07-08 19:06 ` [gentoo-user] " Albert Hopkins
2011-07-08 20:32 ` Stroller
2011-07-09 16:28 ` William Hubbs
2011-07-09 20:24 ` Alan McKinnon
2011-07-08 18:03 ` Stroller
2011-07-08 13:37 ` [gentoo-user] " Nikos Chantziaras
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=4368337.24pI982QGQ@nazgul \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@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