From: Donnie Berkholz <spyderous@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Useflags: qt, qt3, qt4?
Date: Tue, 20 Jun 2006 16:14:08 -0700 [thread overview]
Message-ID: <44988140.2060402@gentoo.org> (raw)
In-Reply-To: <8f5ca2210606201602h4867b91dif9562e631c790239@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
Mike Owen wrote:
> From this user's perspective, simple is better. qt3 and qt4 as use
> flags are completely and utterly obvious as to what they mean, and
> there is no confusion about them. Adding a plain qt flag in there
> brings back the gtk/gtk2 mess that we've presumably been trying to
> avoid in the future.
That depends on how it's done. If it's done in a simple and obvious way
(USE=qt means use the best available qt, USE=qt# for other weird stuff
that most people don't care about and so can ignore), it shouldn't be
that bad.
Thanks,
Donnie
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-06-20 23:17 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 16:40 [gentoo-dev] [RFC] Useflags: qt, qt3, qt4? Stefan Schweizer
2006-06-20 16:56 ` Diego 'Flameeyes' Pettenò
2006-06-20 17:10 ` Joshua Jackson
2006-06-20 17:29 ` Diego 'Flameeyes' Pettenò
2006-06-20 18:00 ` Marius Mauch
2006-06-20 19:18 ` Steve Dibb
2006-06-20 19:54 ` Marius Mauch
2006-06-20 17:15 ` Harald van Dijk
2006-06-20 17:41 ` Simon Stelling
2006-06-20 17:49 ` Steev Klimaszewski
2006-06-20 17:51 ` Diego 'Flameeyes' Pettenò
2006-06-20 19:11 ` Caleb Tennis
2006-06-20 20:05 ` Donnie Berkholz
2006-06-20 20:20 ` Caleb Tennis
2006-06-20 21:07 ` Henrik Brix Andersen
2006-06-20 21:22 ` Donnie Berkholz
2006-06-20 22:45 ` Kevin F. Quinn
2006-06-20 22:52 ` Donnie Berkholz
2006-06-20 23:26 ` Diego 'Flameeyes' Pettenò
2006-06-21 0:12 ` Donnie Berkholz
2006-06-21 0:25 ` Diego 'Flameeyes' Pettenò
2006-06-21 1:06 ` Donnie Berkholz
2006-06-21 1:21 ` Diego 'Flameeyes' Pettenò
2006-06-21 1:34 ` Donnie Berkholz
2006-06-21 1:44 ` Dan Meltzer
2006-06-21 1:46 ` Diego 'Flameeyes' Pettenò
2006-06-21 2:07 ` Donnie Berkholz
2006-06-21 7:57 ` George Shapovalov
2006-06-21 8:36 ` Jakub Moc
2006-06-21 13:45 ` Donnie Berkholz
2006-07-14 19:09 ` Paul de Vrieze
2006-07-14 19:45 ` Harald van Dijk
2006-06-21 20:00 ` Henrik Brix Andersen
2006-06-21 7:03 ` [gentoo-dev] " Stefan Schweizer
2006-06-20 23:02 ` [gentoo-dev] " Mike Owen
2006-06-20 23:14 ` Donnie Berkholz [this message]
2006-06-21 6:12 ` Kevin F. Quinn
2006-06-21 6:25 ` Donnie Berkholz
2006-06-21 9:32 ` Kevin F. Quinn
2006-06-21 13:46 ` Donnie Berkholz
2006-06-21 6:39 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2006-06-21 8:58 ` Kevin F. Quinn
2006-06-21 11:24 ` Diego 'Flameeyes' Pettenò
2006-06-21 13:21 ` [gentoo-dev] " Caleb Tennis
2006-06-21 13:44 ` [gentoo-dev] " Stefan Schweizer
2006-06-21 14:03 ` Donnie Berkholz
2006-06-21 14:03 ` Caleb Tennis
2006-06-21 22:11 ` [gentoo-dev] " Duncan
2006-06-21 22:17 ` Dan Meltzer
2006-06-21 15:20 ` [gentoo-dev] " Carsten Lohrke
2006-06-21 17:08 ` Harald van Dijk
2006-06-25 21:51 ` Ryan Hill
2006-06-21 18:10 ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2006-06-21 19:43 ` Caleb Tennis
2006-06-21 13:48 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
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=44988140.2060402@gentoo.org \
--to=spyderous@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