| 1 |
On Tue, 20 Jun 2006 23:25:42 -0700 |
| 2 |
Donnie Berkholz <spyderous@g.o> wrote: |
| 3 |
|
| 4 |
> Kevin F. Quinn wrote: |
| 5 |
> > On Tue, 20 Jun 2006 16:14:08 -0700 |
| 6 |
> > Donnie Berkholz <spyderous@g.o> wrote: |
| 7 |
> > |
| 8 |
> > [...] |
| 9 |
|
| 10 |
Thanks for the clarification |
| 11 |
|
| 12 |
> The goal is to avoid a double-flag combo to do a single thing. "qt" |
| 13 |
> always and only affects the _best_ available qt interface for that |
| 14 |
> package. "qt#" affects only _older_ available qt interfaces for that |
| 15 |
> package. |
| 16 |
|
| 17 |
OK; so with this we're not providing a way to get an "only qt3" system |
| 18 |
or "only qt4" via USE flags. Perhaps users can do that with local |
| 19 |
masking, provided ebuilds that can build against both depend on all the |
| 20 |
relevant versions: |
| 21 |
|
| 22 |
qt? || ( =dev-libs/qt-3.3* =dev-libs/qt-4.1* ) |
| 23 |
|
| 24 |
-- |
| 25 |
Kevin F. Quinn |
Archives