On 03/11/12 20:01, Pacho Ramos wrote: > After reading previous discussion: > http://help.lockergnome.com/linux/gentoo-dev-Deprecate-EAPIs--ftopict530567.html > > Looks like preventing NEW commits from using eapi1 (via repoman) could > be done without major issues. This could even being done also for eapi2 > as it's close enough to eapi3, but I don't have a strong opinion about > eapi2 deprecation (personally, I try to always use latest eapi if eclass > allows me to do so). > > Any thoughts on this?
I'd deprecate eapi2 too, we don't need 5 flavours around when we effectively only want to support one (and eapi0 in a few places) I wouldn't mind having a deprecation timeline for eapi3 too (now +6 months maybe?), but there's no need to rush things.
