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? The current default, if EAPI is not specified, is EAPI 0. What I'm getting at is... can we safely tell portage to assume that all ebuilds with no EAPI declaration are EAPI 1 (or 2 or 3, etc)? Or will that break some ebuilds? Actually, if only a small percentage of ebuilds break, then it might not be too much of an effort to fix that small subset. -- Walter Dnes <waltd...@waltdnes.org> I don't run "desktop environments"; I run useful applications
