| 1 |
"Caleb Tennis" <caleb@g.o> posted |
| 2 |
34384.192.168.2.159.1150898601.squirrel@××××××××××××.com, excerpted below, |
| 3 |
on Wed, 21 Jun 2006 10:03:21 -0400: |
| 4 |
|
| 5 |
> [Stefan Schweizer wrote...] |
| 6 |
>> qt3 - enable optional qt3 support |
| 7 |
>> qt4 - enable optional qt4 support |
| 8 |
> |
| 9 |
> Maybe I just need a little time to warm up to this. :) |
| 10 |
|
| 11 |
This seems simplest here, too. |
| 12 |
|
| 13 |
Deprecate USE=qt. With only 36 packages |
| 14 |
in the tree using it, it shouldn't be difficult. |
| 15 |
|
| 16 |
qt3 for qt3 |
| 17 |
|
| 18 |
qt4 for qt4 |
| 19 |
|
| 20 |
Thus, if either one is possible, no problem. If both are possible without |
| 21 |
conflict, no problem. |
| 22 |
|
| 23 |
The problems then come if one is required and USE=-qt3 -qt4, or in the |
| 24 |
exclusive-or situation of USE=qt3 qt4 or USE=-qt3 -qt4, but only one can be |
| 25 |
supported at once. |
| 26 |
|
| 27 |
In both cases, defaulting to the later one (4 at this point) will be the |
| 28 |
most future proof. make.defaults could include qt3 ATM, which would |
| 29 |
solve the current KDE support problem for many. There may be a few cases |
| 30 |
where defaulting to the later one in exclusive support situations may be |
| 31 |
problematic, and those should be resolved by the package maintainer as |
| 32 |
they would be on an individual case by case basis just as they would be |
| 33 |
for any other USE flag conflicts. In some rare cases, a die with a message |
| 34 |
directing the user to resolve the conflict manually may be necessary, just |
| 35 |
as can very occasionally be necessary in other situations. In most cases, |
| 36 |
however, an einfo explaining the situation should be sufficient, just as |
| 37 |
it normally is with any other USE flag conflicts. |
| 38 |
|
| 39 |
This should be the clearest from a user perspective, and should require |
| 40 |
the minimal amount of package.use magic, yet it remains an option where a |
| 41 |
user finds it necessary. There will be a bit of disruption when KDE4 |
| 42 |
ultimately stabilizes, but handled correctly, it shouldn't be any more of |
| 43 |
a problem than any major version upgrade on a major desktop environment |
| 44 |
would be -- that is, while some problems should be expected (and well |
| 45 |
published in GWN and the like before stabilization), they should be |
| 46 |
resolvable, and temporary. |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
-- |
| 51 |
Duncan - List replies preferred. No HTML msgs. |
| 52 |
"Every nonfree program has a lord, a master -- |
| 53 |
and if you use the program, he is your master." Richard Stallman |
| 54 |
|
| 55 |
-- |
| 56 |
gentoo-dev@g.o mailing list |
Archives