>>>>> On Fri, 31 Dec 2010, Jeroen Roovers wrote: > I don't see a reason to deprecate an EAPI, unless you are out to > stop a specific feature from being used that was introduced in a > later EAPI and breaks the earlier EAPI. Those ebuilds should be > converted or otherwise taken care of, but it still wouldn't > deprecate the older EAPI as a whole.
The package manager has to support all EAPIs indefinitely. And it also doesn't make sense to convert existing ebuilds when half of the tree is still at EAPI 0. The suggestion is that EAPI >= 2 should be used for _new_ ebuilds. And yes, the old EAPIs are a burden. For example, changing reverse dependencies if USE dependencies are needed. It's no fun if half of the affected ebuilds have to be changed from EAPI 0 to EAPI 2 in such a case. Ulrich
