1 |
Harald van Dijk wrote: |
2 |
> On Wed, Jun 21, 2006 at 05:20:47PM +0200, Carsten Lohrke wrote: |
3 |
>> On Wednesday 21 June 2006 15:44, Stefan Schweizer wrote: |
4 |
>>> qt3 - enable optional qt3 support |
5 |
>>> qt4 - enable optional qt4 support |
6 |
>> That will be a mess to support in the long run. |
7 |
> |
8 |
> Why? |
9 |
|
10 |
Ditto. Can anyone explain why this is bad? |
11 |
|
12 |
I simply don't want QT 4 on my system at this time. Just like I don't want |
13 |
GTK+-1 on my system. Already I've had to start adding packages to package.use |
14 |
with -qt to avoid pulling in qt4 (right next to all my -gtk entries). I don't |
15 |
see how it helps anyone to have a single 'qt' flag that changes meanings |
16 |
depending on the package it's used with. |
17 |
|
18 |
Dan Meltzer wrote: |
19 |
> When do you propose qt4 hits make.defaults? When kde4 hits p.mask, |
20 |
> when it hits ~arch, or when it hits arch? |
21 |
|
22 |
When it hits arch I guess. KDE itself won't be affected by the flag since it's |
23 |
not an optional dependency, and anyone building packages with optional KDE |
24 |
support should be using the kde flag, not qt, so I don't really see how this is |
25 |
relevant. But anyone building packages with optional KDE support will be |
26 |
expecting them to work with the latest stable version. |
27 |
|
28 |
--de. |