1 |
Hi, |
2 |
|
3 |
with kde4 approaching and the new Qt-4 being in the tree we suddenly see the |
4 |
same problems that gtk had with the gtk2 flag again. |
5 |
|
6 |
I am currently using the flags that way: |
7 |
[ebuild R ] app-text/poppler-bindings-0.5.3 USE="cairo gtk qt qt4" 0 kB |
8 |
|
9 |
so qt = qt3. Now that scheme will sure break when people start using the qt |
10 |
useflag for applications that only use qt4. Now cardoe thinks a qt3 useflag |
11 |
would make sense to disable qt3 support easily: |
12 |
|
13 |
sys-apps/dbus-0.62 USE="X gtk mono python -qt3 qt4 -debug -doc" 0 kB |
14 |
|
15 |
I do not think it there should be different useages of the qt, qt3 and qt4 |
16 |
useflag all over the tree, so there are a few options: |
17 |
|
18 |
1) enable qt4 and qt3 by default when both are possible, and merge the qt4 |
19 |
and qt3 useflags currently in the tree into one qt useflag. What we lose |
20 |
here is use.masking qt4, I think this will only be an option when qt4 is |
21 |
marked for all architectures that qt3 is marked for. |
22 |
|
23 |
2) use qt for qt3 only and a special qt4 for qt4. This is what I did |
24 |
originally and it makes sense if done right. However when paackages with |
25 |
qt4 start using the qt4 useflag you can no longer do USE="-qt" to disable |
26 |
qt3 and the concept breaks. |
27 |
|
28 |
3) split the qt flag into a qt3 and a qt4 flag. This allows users to |
29 |
specifically pick qt3 or qt4 and the flag meanings are obvious - downsides |
30 |
are it is a lot of work. |
31 |
|
32 |
4) do nothing and happyly use the qt useflag for qt3 or qt4 as well as |
33 |
sometimes a qt3 useflag or a qt4 useflag, just how the maintainer likes |
34 |
it :) This is also not that bad since we do not need to set any rules here. |
35 |
But it might be confusing and makes it impossible to disable all qt3 uses |
36 |
or all qt4 uses |
37 |
|
38 |
Currently we are at 4), should we change anything? |
39 |
|
40 |
Regards, |
41 |
Stefan |
42 |
|
43 |
-- |
44 |
gentoo-dev@g.o mailing list |