From: "Harald van Dijk" <truedfx@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Useflags: qt, qt3, qt4?
Date: Tue, 20 Jun 2006 19:15:17 +0200 [thread overview]
Message-ID: <20060620171517.GA3256@gentoo.org> (raw)
In-Reply-To: <200606201857.18231@enterprise.flameeyes.is-a-geek.org>
On Tue, Jun 20, 2006 at 06:56:58PM +0200, Diego 'Flameeyes' Pettenò wrote:
> On Tuesday 20 June 2006 18:40, Stefan Schweizer wrote:
> > 3) split the qt flag into a qt3 and a qt4 flag. This allows users to
> > specifically pick qt3 or qt4 and the flag meanings are obvious - downsides
> > are it is a lot of work.
> I would like migration to this idea, that would have been what I've liked to
> see for gtk too.
Same here, both for gtk and for qt. Also, with qt it's slightly worse
than with gtk: qt3 and qt4 are both huge, so if at all possible, I'd
like to not see a requirement to install both qt3 and qt4 just to get
poppler-bindings support for one (which would be required with a single
flag).
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-20 17: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 [this message]
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 ` [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=20060620171517.GA3256@gentoo.org \
--to=truedfx@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