On Wednesday 21 June 2006 15:21, Caleb Tennis wrote:
> Solution: The qt flag represents the latest qt major version for the
> package.   The maintainer can either put in another flag for the older
> version (qt3?) or provide a separate package (e.g. dbus-qt3 ).
Although I can see why you suggest this (Qt 4 is what should become mainline 
asap), right now I think it's going to be a bit of a mess for KDE users, 
Remember we don't have use-deps and that splitting packages is something 
that, if done without upstream support, can give very bad headaches (we both 
know how KDE split is right now).

Also, this puts us back again in gtk's system, with different meaning for the 
same flag (qt can then either be for Qt3 or Qt4, no clear distinction), that 
might even change on maintainer's decision, becoming a mess to handle in 
dependent packages.

Why you think it's better this way rather than having one meaning every 
useflag?

Another thing that this setup is going to make incredibly difficult to manage 
is use.mask masking on profiles. If for some reasons Qt3 or Qt4 needs to be 
masked on a profile, even temporarily, by having qt mean one or the other 
depending on the package is going to be a mess as we don't have per-package 
use.mask (and we won't have till portage 2.2 gets the main scene). This is 
another of the main reasons I don't think it's a good idea to overload 
useflags with different (albeit slightly) meanings.

I agree on the other part tho, pushing Qt4 is indeed a good idea, although it 
might mess up the look&feel of a desktop, but that is marginally important.

-- 
Diego "Flameeyes" Pettenò - http://farragut.flameeyes.is-a-geek.org/
Gentoo/Alt lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE