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