On Fri, 12 Oct 2012 16:38:06 -0400 "Walter Dnes" <waltd...@waltdnes.org> wrote: > On Fri, Oct 12, 2012 at 12:53:15PM +0200, Ralph Sennhauser wrote > > From time to time the topic of deprecating EAPIs comes up and > > usually one suggestion is to keep 0 and start with converting EAPI > > 1 ebuilds. Then someone comes along and asks what is the point? > > Indeed, a fair question. > > It's my understanding that higher EAPI levels include more features. > How backwards compatable are the EAPI levels? I.e. assume that we > take an ebuild with EAPI 0, and slap in EAPI=1 (or 2 or 3, etc) at > the top, without any other changes. Are there any circumstances > where the ebuild would behave differently and/or break?
In EAPIs after 1, as well as adding shiny new toys, we've removed various deprecated things, split up phase functions, and made some helpers error on invalid input. -- Ciaran McCreesh
signature.asc
Description: PGP signature
