El dom, 11-03-2012 a las 13:01 +0100, Pacho Ramos escribió: > 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? > > Thanks
Well, the reasons for me preferring to not allow *new* ebuilds to use eapi1 is to try to move to use things like, for example, src_prepare/src_configure phases. I guess that phases were included for some "technical" reasons and, then, I think we should try to use them if possible install of still adding NEW ebuilds using old eapi0/1 way of doing things
signature.asc
Description: This is a digitally signed message part
