| 1 |
Hmm...Are thre any packages out there which *must* be built against |
| 2 |
the same qt as (the rest of) kde? If so, I don't think qt4 should be |
| 3 |
in the default use flags until KDE4 hits arch. This keeps people from |
| 4 |
reporting issues with KDE apps built against the wrong version of QT. |
| 5 |
|
| 6 |
--Arek |
| 7 |
|
| 8 |
On 6/23/06, Stefan Schweizer <genstef@g.o> wrote: |
| 9 |
> Caleb Tennis wrote: |
| 10 |
> > 2) Remove qt use flag, and create qt3 and qt4 global flags. |
| 11 |
> |
| 12 |
> It allows proper use.masking. |
| 13 |
> Thanks. |
| 14 |
> |
| 15 |
> > people who are in favor of #2 have volunteered to do the work to implement |
| 16 |
> > it as well as put qt3 into the use.defaults for 2006.1 so KDE will work |
| 17 |
> > "out of the box". |
| 18 |
> |
| 19 |
> What should happen to qt4? I think it should be in make.defaults because qt |
| 20 |
> is in make.defaults. So initially we need to do for make defaults: |
| 21 |
> s/qt/qt qt3 qt4/ |
| 22 |
> |
| 23 |
> I would like this to happen retroactively for all current profiles so that |
| 24 |
> no one gets broken when we migrate all ebuilds. After the conversion the qt |
| 25 |
> use flag can be removed from the profiles. |
| 26 |
> |
| 27 |
> waiting for qt3 default flag to migrate my ebuilds :) |
| 28 |
> |
| 29 |
> Regards, |
| 30 |
> Stefan |
| 31 |
> |
| 32 |
> -- |
| 33 |
> gentoo-dev@g.o mailing list |
| 34 |
> |
| 35 |
> |
| 36 |
-- |
| 37 |
gentoo-dev@g.o mailing list |
Archives