On Mon, Jul 14, 2008 at 5:32 AM, Jeroen Roovers <[EMAIL PROTECTED]> wrote:
>
> What GLEP 55 fails to address right now is the very development process
> it is seemingly supposed to alleviate. It addresses the issue of EAPI
> implementation from the viewpoint of the package manager's developer,
> but it doesn't begin to address the viewpoint of the package
> maintainer or architecture developer at all. It looks to me like a lot
> of problems are moved out of the package manager(s) and into this
> already huge tree of files, with different EAPI-suffixed files
> addressing different problems, and that indicate be a non-trivial
> increase in the number of files in the tree - files which would
> address the equal purpose of installing exactly one =cat/pkg-ver.

GLEP 55 says:
"Note that it is still not permitted to have more than one ebuild with
equal category, package name, and version."

> In other words, disregarding its other real world deficiencies like an
> immediate goal, GLEP 55 fails to describe a keywording policy for
> architecture developers

Keywording policy wouldn't change.

Regards,
-- 
Santiago M. Mola
Jabber ID: [EMAIL PROTECTED]
-- 
gentoo-dev@lists.gentoo.org mailing list

Reply via email to