1 |
What's not clear with 'apropriate' word in my sentence? |
2 |
|
3 |
Let me clarify - if package depend either on Qt4 or Qt5 and CAN not be |
4 |
built with Qt at all - force this behaviour with REQUIRED_USE. |
5 |
|
6 |
I think that it was obvious that i have meant exactly this case, cause |
7 |
other cases are unreasonable here. |
8 |
|
9 |
09.08.2015 23:07, Alexandre Rostovtsev пишет: |
10 |
> On Sun, 2015-08-09 at 22:38 +0300, Sergey Popov wrote: |
11 |
>> <qa team lead hat> |
12 |
>> |
13 |
>> In short - apropriate REQUIRED_USE with setting recommended |
14 |
>> USE-flag(e.g. USE="+qt4 qt5" or USE="qt4 +qt5") |
15 |
>> |
16 |
>> </qa team lead hat> |
17 |
> |
18 |
> If a package has optional guis, why should users of the default profile get any |
19 |
> gui enabled by default? The default profile usually means "headless server". It |
20 |
> means users who specifically don't need gtk, don't need qt4, don't need qt5, |
21 |
> don't need X. |
22 |
> |
23 |
> So please don't + desktop-oriented USE flags in an ebuild's IUSE by default |
24 |
> unless the whole ebuild is intended mainly for desktop users. |
25 |
> |
26 |
>> Users will have default behaviour for empty make.conf. If they adjust |
27 |
>> they make.conf to globally include/exclude some Qt-related USEs - they |
28 |
>> are already moving from default and that's why - they can add apropriate |
29 |
>> options to package.use |
30 |
> |
31 |
> There is more than one "default" from which to move away. Different profiles |
32 |
> globally enable different flags. Desktop, gnome, and kde profiles already enable |
33 |
> qt4 globally. Plasma already enables qt4 and qt5 globally. And the desktop |
34 |
> profile will probably end up enabling qt4 and qt5 at some point. |
35 |
> |
36 |
|
37 |
|
38 |
-- |
39 |
Best regards, Sergey Popov |
40 |
Gentoo developer |
41 |
Gentoo Desktop Effects project lead |
42 |
Gentoo Quality Assurance project lead |
43 |
Gentoo Proxy maintainers project lead |