| 1 |
Hi, |
| 2 |
|
| 3 |
following szenario: Somebody installs a kde desktop and because of it is |
| 4 |
an 80 years old woman ;), she wants to have graphical frontends where |
| 5 |
ever possible. |
| 6 |
|
| 7 |
Today the solution would be to enable the kde, qt, qt3, qt4, gtk, etc. |
| 8 |
-useflag. But this solution is crappy, because of some ebuilds for |
| 9 |
example app-office/openoffice have support for multiple widget libraries |
| 10 |
and because our 80 years old female person has a kde desktop, she would |
| 11 |
prefer kde-support about gtk+. Today she would have to decide if she |
| 12 |
wants to make an entry in /etc/portage/package.use for each ebuild that |
| 13 |
comes with multiple widget library support or if she wants to compile |
| 14 |
each such ebuild preventive with support for every available widget |
| 15 |
library, which would be against the sense of useflags. |
| 16 |
|
| 17 |
To prevent such szenarios I propose following extended syntax for |
| 18 |
useflag configuration: |
| 19 |
|
| 20 |
(kde || qt4 || qt3 || qt || gtk) (arts || alsa) (asf && win32codecs) |
| 21 |
|
| 22 |
This expression would affect that only if a kde-useflag isn't provided |
| 23 |
the qt4 useflag, becomes used and if this isn't also provided the qt3 |
| 24 |
useflag becomes used and so on. The same for arts and alsa, where it is |
| 25 |
nonsense to support both but better to support arts. And the last |
| 26 |
segment of this expression would affect that win32codecs and asf becomes |
| 27 |
enabled for each ebuild that supports asf. This would for example be |
| 28 |
useful in the case of media-libs/xine-lib if you want have asf-support |
| 29 |
but you want avoid win32codecs as much as possible, because of xine-lib |
| 30 |
needs win32codecs to support asf. |
| 31 |
|
| 32 |
Best Regards |
| 33 |
Sebasitan Noack |
| 34 |
|
| 35 |
-- |
| 36 |
gentoo-dev@g.o mailing list |
Archives