| 1 |
On Mon, Jul 14, 2008 at 5:32 AM, Jeroen Roovers <jer@g.o> wrote: |
| 2 |
> |
| 3 |
> What GLEP 55 fails to address right now is the very development process |
| 4 |
> it is seemingly supposed to alleviate. It addresses the issue of EAPI |
| 5 |
> implementation from the viewpoint of the package manager's developer, |
| 6 |
> but it doesn't begin to address the viewpoint of the package |
| 7 |
> maintainer or architecture developer at all. It looks to me like a lot |
| 8 |
> of problems are moved out of the package manager(s) and into this |
| 9 |
> already huge tree of files, with different EAPI-suffixed files |
| 10 |
> addressing different problems, and that indicate be a non-trivial |
| 11 |
> increase in the number of files in the tree - files which would |
| 12 |
> address the equal purpose of installing exactly one =cat/pkg-ver. |
| 13 |
|
| 14 |
GLEP 55 says: |
| 15 |
"Note that it is still not permitted to have more than one ebuild with |
| 16 |
equal category, package name, and version." |
| 17 |
|
| 18 |
> In other words, disregarding its other real world deficiencies like an |
| 19 |
> immediate goal, GLEP 55 fails to describe a keywording policy for |
| 20 |
> architecture developers |
| 21 |
|
| 22 |
Keywording policy wouldn't change. |
| 23 |
|
| 24 |
Regards, |
| 25 |
-- |
| 26 |
Santiago M. Mola |
| 27 |
Jabber ID: cooldwind@×××××.com |
| 28 |
-- |
| 29 |
gentoo-dev@l.g.o mailing list |
Archives