1 |
<qa team lead hat> |
2 |
|
3 |
In short - apropriate REQUIRED_USE with setting recommended |
4 |
USE-flag(e.g. USE="+qt4 qt5" or USE="qt4 +qt5") |
5 |
|
6 |
</qa team lead hat> |
7 |
|
8 |
That's most painless decision for both developers and users. Developers |
9 |
do not need to maintain ugly dependencies like |
10 |
|
11 |
DEPEND="qt4 ? ( |
12 |
qt5 ( dev-qt/qtcore:5 ) |
13 |
!qt5 ( dev-qt/qtcore:4 ) |
14 |
) |
15 |
... |
16 |
" |
17 |
and other mess. |
18 |
|
19 |
</qa team lead hat> |
20 |
|
21 |
Users will have default behaviour for empty make.conf. If they adjust |
22 |
they make.conf to globally include/exclude some Qt-related USEs - they |
23 |
are already moving from default and that's why - they can add apropriate |
24 |
options to package.use |
25 |
|
26 |
|
27 |
02.08.2015 19:34, Ben de Groot пишет: |
28 |
> Recently some team members of the Qt project have adopted these ebuild |
29 |
> policies: https://wiki.gentoo.org/wiki/Project:Qt/Policies |
30 |
> |
31 |
> I have an issue with the policy adopted under "Requires one of two Qt |
32 |
> versions". In my opinion, in the case where a package offers a choice |
33 |
> between qt4 or qt5, we should express this in explicit useflags and a |
34 |
> REQUIRED_USE="^^ ( qt4 qt5 )". This offers the user the clearest choice. |
35 |
> |
36 |
> Other developers state that users are not interested in such |
37 |
> implementation details, or that forced choice through REQUIRED_USE is |
38 |
> too much of a hassle. This results in current ebuilds such as quassel to |
39 |
> not make it clear that qt4 is an option. |
40 |
> |
41 |
> This goes against the principle of least surprise, as well as against QA |
42 |
> recommendations. I would like to hear specifically from QA about how we |
43 |
> should proceed, but comments from the wider developer community are also |
44 |
> welcome. |
45 |
> |
46 |
> -- |
47 |
> Cheers, |
48 |
> |
49 |
> Ben | yngwin |
50 |
> Gentoo developer |
51 |
> |
52 |
|
53 |
|
54 |
-- |
55 |
Best regards, Sergey Popov |
56 |
Gentoo developer |
57 |
Gentoo Desktop-effects project lead |
58 |
Gentoo Quality Assurance project lead |
59 |
Gentoo Proxy maintainers project lead |