From: Carsten Lohrke <carlo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] Useflags: qt, qt3, qt4?
Date: Wed, 21 Jun 2006 17:20:47 +0200 [thread overview]
Message-ID: <200606211720.56203.carlo@gentoo.org> (raw)
In-Reply-To: <e7bigq$93k$1@sea.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
On Wednesday 21 June 2006 15:44, Stefan Schweizer wrote:
> qt3 and qt4 is being used there already and it is obvious
It's "nice" to invent new use flags affecting Qt stuff without contacting
those who care for Qt.
>
> > 2) A package requires either Qt3 or Qt4 (both not both?...such as
> > x11-libs/qwt-5).
>
> qt3 - enable optional qt3 support
> qt4 - enable optional qt4 support
That will be a mess to support in the long run. Let's go with that what works
better, prefer the latest version and be fine with it. I do agree with Caleb
to use the qt use flag for the latest supported version and in cases it is
really necessary to have an additional qt3 use flag.
Carsten
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2006-06-21 16:31 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
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 ` Carsten Lohrke [this message]
2006-06-21 17:08 ` [gentoo-dev] " 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=200606211720.56203.carlo@gentoo.org \
--to=carlo@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