Ryan Hill wrote: > (Yes, this has EAPI in the title, so that means everyone will chime in) > > I'd like to clarify and (eventually) set in stone our ideas of best practices > when it comes to bumping EAPI for system packages. I was of the belief that > we had decided that system packages should remain at EAPI 0 for > backwards-compatibility reasons. It seems, however, that this was never > written down anywhere and today we find ourselves in a situation where it is > impossible to bootstrap a Gentoo system from a pre-EAPI-era liveCD due to all > python versions being EAPI 1 or later. Maybe we don't care anymore, but I'd > like to know what people think. >
I think the consensus was / is? that the upgrade path from EAPI 0 should have existed until we decide to not support it anymore and the decision should not have been made by for example python maintainers. The only packages that matter are Portage dependencies not the full system target. Basically you need to be able to upgrade your Portage and use the new version. Regards, Petteri
signature.asc
Description: OpenPGP digital signature
