We have to be precise about what we are talking here: 1) for NEW ebuilds added to the tree... > > So maybe it's about time that we deprecate EAPIs 0 and 1 for new > ebuilds. As a first step, a warning could be added to repoman that > would be triggered whenever a new ebuild with an EAPI less than 2 is > committed.
it would definitely make sense to trigger a warning whenever an ancient EAPI is used. Remember, we're adding new features so we can use them - and we also want to train new recruits for using these features. So, I'm for a repoman warning for NEW ebuilds whenever EAPI<(CURRENT_EAPI-1). This would at the moment deprecate EAPI=0,1 (and soon also 2). 2) for existing ebuilds... ... it is indeed impractical to force EAPI=0 rewriting. Some of the in-between steps however should be deprecated. Eg. EAPI=1 and later EAPI=2... My 2ct... Cheers, Andreas -- Andreas K. Huettel [email protected] http://www.akhuettel.de/
signature.asc
Description: This is a digitally signed message part.
