On Thu, Oct 18, 2012 at 11:49 AM, Pacho Ramos <pa...@gentoo.org> wrote: > I didn't think eapi4 features were still "unfamiliar" to so many > people... let's say, what about deprecating eapi1, 2 and 0 for newer > ebuilds? Is eapi2 so unfamiliar also to not force it as older eapi for > newer ebuilds (eapi3 changes look to be minor when compared with > eapi2) ?
This still involves the issue that what would be simple ebuild bumps turn into a need to make more substantial changes to an ebuild. And the concern still exists that a policy that says all new ebuilds shall use EAPI foo might result in fewer new ebuilds. Sure, they'll have new and shiny fooness, but arguably I'd rather have more packages supported on older EAPIs then fewer packages supported on newer ones. If migrating to newer EAPIs is so simple, why aren't more doing it already? Rich
