| 1 |
On Monday 27 of April 2009 16:19:31 Duncan wrote: |
| 2 |
|
| 3 |
[snip] |
| 4 |
> But even before that it was a pain, because it didn't follow the |
| 5 |
> intuitive idea that USE=gtk meant gtk1 support while USE=gtk2 meant gtk2 |
| 6 |
> support. New users very often enabled gtk2 without enabling gtk, |
| 7 |
> believing they were expressing a desire for gtk2 support but NOT gtk1, |
| 8 |
> when instead what it was really expressing was, don't support gtk (of any |
| 9 |
> version) unless you have to, but if it's mandatory and there's a choice, |
| 10 |
> choose gtk2 over gtk1. |
| 11 |
[snip] |
| 12 |
|
| 13 |
It's good that Alexxy raised this issue. |
| 14 |
And I actually support Duncan here. |
| 15 |
Good thing is - there are not that many packages with newly added 'kde' USE |
| 16 |
flags that refer to KDE4. |
| 17 |
If some package provides support for both KDE3 and KDE4 - there's no other |
| 18 |
option but to add kde3 and kde4 USE flags if it's meant to be obvious and |
| 19 |
descriptive for users. |
| 20 |
And what does 'general KDE support mean for' when 'kde' USE flag is provided? |
| 21 |
Usually KDE support means required presence of kdelibs, and... one simply |
| 22 |
cannot compile same code against kdelibs from KDE3 and KDE4 - so it should be |
| 23 |
distinguished somehow - otherwise users would need to adjust package.use. |
| 24 |
Introducing kde3, kde4 USE flags, users at least are able to globally |
| 25 |
(make.conf) decide whether they care about KDE support for KDE they have. |
| 26 |
|
| 27 |
-- |
| 28 |
regards |
| 29 |
MM |
Archives