| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
Hey all -- there was just a discussion in #gentoo-dev about this, so |
| 5 |
following up here.. |
| 6 |
|
| 7 |
Due to the fact that an EAPI-bump can imply different behaviour from |
| 8 |
eclasses or the PM, an EAPI-bump should in most cases also require an |
| 9 |
ebuild revbump. |
| 10 |
|
| 11 |
Why i'm bringing this up here, is because Chansaw and I were wondering |
| 12 |
if common sense will not be enough to ensure this and it should be |
| 13 |
made a policy to revbump when migrating to a new EAPI ? |
| 14 |
|
| 15 |
-----BEGIN PGP SIGNATURE----- |
| 16 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 17 |
|
| 18 |
iF4EAREIAAYFAlCBWwsACgkQ2ugaI38ACPDq9QEAv4dtB8q5h4k6P5Fcl5KJ6AZz |
| 19 |
+stbD96s7kNG5cLu1zcBAJ/iyTOvAH5GIYhnSDKOrz2JODD7Zq0II9W+7L4XMfQa |
| 20 |
=03Pd |
| 21 |
-----END PGP SIGNATURE----- |
Archives