>>>>> On Wed, 03 Nov 2021, Andreas K Huettel wrote: > The mistake was to allow the use of EAPI=8 too early. In the future, > we should have a new EAPI supported by portage for at least some > months before the EAPI is even used in the main tree. Not even > speaking about stable here.
I tend to disagree. Adding an ebuild with a new EAPI cannot break anything, because it will simply be invisible to old package managers. There won't be a problem unless you _remove_ ebuilds that are part of the upgrade path. Ulrich
signature.asc
Description: PGP signature
