Taking a random commit to explain a recent-yet-common mistake. > dev-python/subunit: Add python3.5 support > > [...] > > dev-python/subunit/subunit-1.1.0-r1.ebuild | 90 > ++++++++++++++++++++++++++++++ > 1 file changed, 90 insertions(+)
Let's make this clear once and for all: there is no need to revbump when adding python3.5 to PYTHON_COMPAT, and this includes stable packages. This is because: 1. adding it to PYTHON_COMPAT adds a new USE flag, and the added dependency is conditional to the USE flag. People who have the package installed already don't have python3.5 support in it and don't need the new dependency. People who want python3.5 will get the package rebuilt due to --changed-use or cross-package USE dependencies. 2. python_targets_python3_5 is stable-masked. This means that the new flag simply won't appear on stable packages until python3.5 goes stable. No need to play with keywords. So once again: please don't bump packages unnecessarily when adding python3.5 to PYTHON_COMPAT. However, if you add new patches or other ebuild code changes, revbump is desired. -- Best regards, Michał Górny <http://dev.gentoo.org/~mgorny/>
pgpAIjEBKLF26.pgp
Description: OpenPGP digital signature
