-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Remind me and the list again pls, why is this necessary rather than
just using use.stable.mask and EAPI5 ebuilds in the regular profiles?
This shouldn't break the tree with a non-EAPI5 portage as the files
would just be ignored, as would the EAPI5 ebuilds.....

For some core stuff (like portage) i could see this as being an issue
but we aren't going to need to use.stable.mask flags on core packages
are we?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlDLOjwACgkQ2ugaI38ACPAaugD/frwJ+kv9w49o1vPGQfLD0uQT
nj2pVXrks/RYUZp+PL8A/1JYcKdzlAup+LIpY/uQzcGwqmtS3U34ZzM7vG+CRQ70
=nXpr
-----END PGP SIGNATURE-----

Reply via email to