Jan Kundrát wrote:
> If the user knows that keywords are set by the KEYWORDS variable, then
> she must be familiar with the EAPI. The meaning of the KEYWORDS variable
> is defined by the EAPI.

But that's not really what I find objectionable.  There's no need to
make EAPI so special that it alters the file extension.  If EAPI is
accessible as part of the file or in metadata.xml, e.g., it still serves
this purpose well, and that info is exposed at the right level.

> Sure. If current EAPI specified that a sequence of four bytes starting
> at offset  0x10 is a little-endian magic number that is used to identify
> an EAPI, that'd be all we want. However, current format definition is
> rather complex; there's nothing as simple as "read several bytes at some
> offset and use them".

I would not suggest byte-level methods, no - these files are not binary.
 There are simple ways to parse text files to find the EAPI.  If it is
in the ebuild, putting it in the header (out-of-band) works.  If it is
in metadata, simply parsing XML works.

						-Joe
-- 
gentoo-dev@g.o mailing list