| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 17/11/15 05:45 PM, Michael Orlitzky wrote: |
| 5 |
> On 11/17/2015 05:09 PM, Michał Górny wrote: |
| 6 |
>> Fellow Developers! |
| 7 |
>> |
| 8 |
>> I have the pleasure to announce that portage-2.2.25 has just |
| 9 |
>> been committed and it comes with complete EAPI 6 support. This |
| 10 |
>> effectively means that from this moment forward Gentoo |
| 11 |
>> developers are permitted to commit EAPI 6 ebuilds to ~arch. |
| 12 |
>> |
| 13 |
> |
| 14 |
> Thanks for all the work on this and the guide. |
| 15 |
> |
| 16 |
> Is it really safe to start committing ~arch ebuilds that don't |
| 17 |
> work with stable portage? Might not things get wonky for stable |
| 18 |
> users who have a few keyworded packages? |
| 19 |
> |
| 20 |
> For developers, is my stable version of repoman smart enough to |
| 21 |
> make sure I don't break any dependencies in this way? |
| 22 |
> |
| 23 |
> |
| 24 |
|
| 25 |
If your PM doesn't support EAPI6, then those ebuilds will be ignored |
| 26 |
just as if they do not exist. It is plenty safe. There can be |
| 27 |
issues if EAPI5 or older ~arch packages start -needing- EAPI6-only |
| 28 |
~arch dependencies, but so long as people are careful (and likely, |
| 29 |
start bumping to EAPI6 along with the dependencies) then things will |
| 30 |
work out without much incident. |
| 31 |
|
| 32 |
|
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v2 |
| 35 |
|
| 36 |
iF4EAREIAAYFAlZLzp4ACgkQAJxUfCtlWe00AAEA5RoB95Z/pvQcqYu+1dDzPh2d |
| 37 |
/MP+kcQdHus14B+SnMsBANZubHScfv/9z75lY3Hub3GnamyPLgtSDGyK43UatKBv |
| 38 |
=m7RY |
| 39 |
-----END PGP SIGNATURE----- |
Archives