Kevin F. Quinn wrote: >> The goal is to avoid a double-flag combo to do a single thing. "qt" >> always and only affects the _best_ available qt interface for that >> package. "qt#" affects only _older_ available qt interfaces for that >> package. > > OK; so with this we're not providing a way to get an "only qt3" system > or "only qt4" via USE flags. Perhaps users can do that with local > masking, provided ebuilds that can build against both depend on all the > relevant versions: > > qt? || ( =dev-libs/qt-3.3* =dev-libs/qt-4.1* )
Yes, I just mentioned elsewhere in the thread that this is a downside of this design. Another possibility is getting rid of USE=qt and having only USE=qt#. Thanks, Donnie
signature.asc
Description: OpenPGP digital signature
