Stephen Bennett wrote: >> My understanding was that the portage team can't move forward with a >> new version until EAPI0 is done? > They can't move forward with changes that break ebuild compatibility > until EAPI-0 is documented and EAPI-1 can start to be defined. That's > not to say that user-side changes which don't affect the ebuild > interface can't happen. Ah ok. Well, given the state of the portage code, I doubt it's worth starting anew until EAPI0 is done, since clearly the team have to do maintenance and improvements in the meanwhile, as so many ppl depend on portage working right. Also, I thought one of the main benefits was making things easier for ebuild devs? Ciaran was himself disdainful of UI improvements.
-- gentoo-dev@gentoo.org mailing list
