On 11/17/2015 08:04 PM, Ian Stakenvicius wrote: > > 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. >
It doesn't seem that unlikely to me... 1. Otherwise stable system with package "foo" keyworded as ~arch. 2. foo needs some dependency of a dependency named "bar". 3. The bar maintainer revbumps and removes the old EAPI=5 ebuild. I don't really care either way, I'm just wondering whether this is "safe" because it's actually safe, or "safe" because we're gonna do it anyway.
