1 |
Taking a random commit to explain a recent-yet-common mistake. |
2 |
|
3 |
> dev-python/subunit: Add python3.5 support |
4 |
> |
5 |
> [...] |
6 |
> |
7 |
> dev-python/subunit/subunit-1.1.0-r1.ebuild | 90 ++++++++++++++++++++++++++++++ |
8 |
> 1 file changed, 90 insertions(+) |
9 |
|
10 |
Let's make this clear once and for all: there is no need to revbump |
11 |
when adding python3.5 to PYTHON_COMPAT, and this includes stable |
12 |
packages. This is because: |
13 |
|
14 |
1. adding it to PYTHON_COMPAT adds a new USE flag, and the added |
15 |
dependency is conditional to the USE flag. People who have the package |
16 |
installed already don't have python3.5 support in it and don't need |
17 |
the new dependency. People who want python3.5 will get the package |
18 |
rebuilt due to --changed-use or cross-package USE dependencies. |
19 |
|
20 |
2. python_targets_python3_5 is stable-masked. This means that the new |
21 |
flag simply won't appear on stable packages until python3.5 goes |
22 |
stable. No need to play with keywords. |
23 |
|
24 |
So once again: please don't bump packages unnecessarily when adding |
25 |
python3.5 to PYTHON_COMPAT. However, if you add new patches or other |
26 |
ebuild code changes, revbump is desired. |
27 |
|
28 |
-- |
29 |
Best regards, |
30 |
Michał Górny |
31 |
<http://dev.gentoo.org/~mgorny/> |