[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    [gentoo-dev]  Re: [RFC] Useflags: qt, qt3, qt4?
From:       Ryan Hill <dirtyepic.sk () gmail ! com>
Date:       2006-06-25 21:51:37
Message-ID: e7n0t2$3ne$1 () sea ! gmane ! org
[Download RAW message or body]

Harald van Dijk wrote:
> On Wed, Jun 21, 2006 at 05:20:47PM +0200, Carsten Lohrke wrote:
>> On Wednesday 21 June 2006 15:44, Stefan Schweizer wrote:
>>> qt3 - enable optional qt3 support
>>> qt4 - enable optional qt4 support
>> That will be a mess to support in the long run.
> 
> Why?

Ditto.  Can anyone explain why this is bad?

I simply don't want QT 4 on my system at this time.  Just like I don't want
GTK+-1 on my system.  Already I've had to start adding packages to package.use
with -qt to avoid pulling in qt4 (right next to all my -gtk entries).  I don't
see how it helps anyone to have a single 'qt' flag that changes meanings
depending on the package it's used with.

Dan Meltzer wrote:
> When do you propose qt4 hits make.defaults? When kde4 hits p.mask,
> when it hits ~arch, or when it hits arch? 

When it hits arch I guess.  KDE itself won't be affected by the flag since it's
not an optional dependency, and anyone building packages with optional KDE
support should be using the kde flag, not qt, so I don't really see how this is
relevant.  But anyone building packages with optional KDE support will be
expecting them to work with the latest stable version.

--de.




["signature.asc" (application/pgp-signature)]
-- 
gentoo-dev@gentoo.org mailing list


[prev in list] [next in list] [prev in thread] [next in thread]