Ryan Hill wrote:
On Mon, 23 Feb 2009 08:43:09 -0700
Steve Dibb <bean...@gentoo.org> wrote:
Richard Freeman wrote:
I still don't see why we need to be encoding metadata in filenames.
PERL doesn't care what a file extension is, python doesn't care,
bzip2 doesn't care, tar doesn't care, gzip doesn't care, and even
ld-linux.so doesn't care. I'm sure that in at least some of these
cases they end up parsing parts of the file twice - once to figure
out what it is, and the second time to actually handle it. I'm
actually hard pressed to think of any unix-based software that uses
the filename to store a mandatory file format versioning specifier
of some kind.
$ ls /usr/lib
ldconfig ?
I have to admit I'm in the same camp with Richard, and don't
understand the necessity. I'm also opposed to creating arbitrary
suffixes to the ebuild extension, for cosmetic and compatibility
reasons.
Plus, I don't really grasp the whole "we have to source the whole
ebuild to know the EAPI version" argument. It's one variable, in one
line. Can't a simple parser get that and go from there?
Not really. Let's play Guess the EAPI. :o
1.
-----
EAPI=1
----
2. (with myeclass.eclass containing EAPI=2)
-----
EAPI=1
inherit myeclass
Invalid
-----
3. (with myeclass.eclass containing EAPI=2)
-----
EAPI=5
inherit myeclass
Invalid
So you see, it's not as easy as a grep command. You need to source the
ebuild to know how things like inherit will affect the environment.
And without knowing the EAPI, you don't know which version of inherit to
call.
It it isn't invalid already...
(i hope i have this right. feel free to call me names if i don't)
Names!
lu
--
Luca Barbato
Gentoo Council Member
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
