--- xml/htdocs/proj/en/glep/glep-0050.txt 2006/06/15 14:36:52 1.1 +++ xml/htdocs/proj/en/glep/glep-0050.txt 2006/06/15 15:29:18 1.2 @@ -1,7 +1,7 @@ GLEP: 50 Title: Supporting alternative package managers -Version: $Revision: 1.1 $ -Last-Modified: $Date: 2006/06/15 14:36:52 $ +Version: $Revision: 1.2 $ +Last-Modified: $Date: 2006/06/15 15:29:18 $ Author: Grant Goodyear Status: Draft Type: Standards Track @@ -49,15 +49,20 @@ being able to build installation media, providing a transition path from or to the existing official package manager, etcetera. -Note -==== +Notes +===== -An early criticism of this GLEP was that it fails to address eclasses and -profiles. As far as eclasses are concerned, my view is that the above rules -suffice, since eclasses only matter in their use in ebuilds. If a package -manager can effectively process all ebuilds, then it must be handling the -eclasses successfully, too. Profiles, on the other hand, are not addressed -here even implicitly. +* An early criticism of this GLEP was that it fails to address eclasses and + profiles. As far as eclasses are concerned, my view is that the above rules + suffice, since eclasses only matter in their use in ebuilds. If a package + manager can effectively process all ebuilds, then it must be handling the + eclasses successfully, too. Profiles, on the other hand, are not addressed + here even implicitly. +* Assuming the ebuild specification is successfully finished, then the + first rule should really replace "all ebuilds supported by the official + package manager" with "all ebuilds that satisfy the ebuild spec". + Similarly, in rule two "by the official package manager" should + read "by the official ebuild spec". Backwards Compatibility =======================