--- xml/htdocs/proj/en/glep/glep-0055.html 2008/01/05 02:42:59 1.1 +++ xml/htdocs/proj/en/glep/glep-0055.html 2008/01/06 02:39:42 1.2 @@ -1,11 +1,7 @@ - + @@ -21,7 +17,7 @@ border="0" width="150" height="35" /> [Gentoo Linux Home] -[GLEP Index] +[GLEP Index] [GLEP Source] @@ -82,10 +78,10 @@ EAPI the package manager needs to source the ebuild, which itself needs the EAPI in the first place. Otherwise it imposes a serious limitation, namely every ebuild, using any of the future EAPIs, will have to be source'able by old package -managers and hence there is no way to:

+managers and hence there is no way to do any of the following:

Note that it is still not permitted to have more than one ebuild with equal category, package name, and version. Although it would have the advantage of -allowing to provide backward compatible ebuilds, it would introduce problems -too. The first is the requirement to have strict EAPI ordering, the second is -ensuring that all the ebuilds for a single category/package-version are -equivalent, i.e. installing any of them has exactly the same effect to the -system.

+allowing authors to provide backwards compatible ebuilds, it would introduce +problems too. The first is the requirement to have strict EAPI ordering, the +second is ensuring that all the ebuilds for a single category/package-version +are equivalent, i.e. installing any of them has exactly the same effect on a +given system.

Application

@@ -208,8 +204,8 @@
@@ -266,7 +262,7 @@