On Wed, 19 Dec 2007 10:26:16 +0000 Steve Long <[EMAIL PROTECTED]> wrote: > Are you really telling me you are going to write _one_ ebuild > with /that/ god-awful hackery in it?
Are you really suggesting that no-one ever will?
> Sticking to a single EAPI="xx" format in the ebuild means we don't
> have the *hack* of duplicating information in the filename (and the
> whole {pre,post}src issue, QA checks for human error since this is
> redundant info) simply to avoid parsing a config file.
There is no duplication of information, nor redundancy.
The pre/post source issue exists regardless of how EAPI is set -- it's
just that with filename EAPIs, you aren't restricted to post source
changes. It's explicit in the GLEP because it's important that package
mangers get it right, but it's not a new issue.
Ebuilds are not config files.
Really. It's a heck of a lot cleaner in the filename suffix.
--
Ciaran McCreesh
signature.asc
Description: PGP signature
