| 1 |
On Sun, 2015-08-09 at 22:38 +0300, Sergey Popov wrote: |
| 2 |
> <qa team lead hat> |
| 3 |
> |
| 4 |
> In short - apropriate REQUIRED_USE with setting recommended |
| 5 |
> USE-flag(e.g. USE="+qt4 qt5" or USE="qt4 +qt5") |
| 6 |
> |
| 7 |
> </qa team lead hat> |
| 8 |
|
| 9 |
If a package has optional guis, why should users of the default profile get any |
| 10 |
gui enabled by default? The default profile usually means "headless server". It |
| 11 |
means users who specifically don't need gtk, don't need qt4, don't need qt5, |
| 12 |
don't need X. |
| 13 |
|
| 14 |
So please don't + desktop-oriented USE flags in an ebuild's IUSE by default |
| 15 |
unless the whole ebuild is intended mainly for desktop users. |
| 16 |
|
| 17 |
> Users will have default behaviour for empty make.conf. If they adjust |
| 18 |
> they make.conf to globally include/exclude some Qt-related USEs - they |
| 19 |
> are already moving from default and that's why - they can add apropriate |
| 20 |
> options to package.use |
| 21 |
|
| 22 |
There is more than one "default" from which to move away. Different profiles |
| 23 |
globally enable different flags. Desktop, gnome, and kde profiles already enable |
| 24 |
qt4 globally. Plasma already enables qt4 and qt5 globally. And the desktop |
| 25 |
profile will probably end up enabling qt4 and qt5 at some point. |
Archives