Piotr Jaroszyński wrote:
> Hello,
>
> attaching the GLEP.
>
> most current version:
> http://dev.gentoo.org/~peper/glep-0055.html
> http://dev.gentoo.org/~peper/glep-0055.txt
>
>
> Abstract
> ========
> This GLEP proposes usage of EAPI-suffixed file extensions for ebuilds
> (for example, foo-1.2.3.ebuild-1).
I probably missed some of the stuff leading up to this GLEP, but what is
the problem with having the EAPI in the file and determining it by
looking at the file contents?
Making the file extension variable by adding "-<EAPI>" to it would, in
my opinion, make the portage tree a bit less clean and not as elegant.
Wouldn't software (like editors determining file type by looking at what
is after the ".") also need to be reworked to recognize a variable
string after "-" at the end?
I imagine a lot of people do things now like 'find . -name "*.ebuild" |
xargs grep ...'. Not that they could not change their habbits, but
forgetting to add a more complex matching rule could lead to errors
here. It just seems to me that adding complexity to what is basically a
file extension is undesirable unless there is a very good reason why it
cannot be done a different way.
-Joe
--
[EMAIL PROTECTED] mailing list
