Ciaran McCreesh wrote:
On Mon, 23 Feb 2009 19:17:19 -0500
Richard Freeman <ri...@gentoo.org> wrote:
It just seems like it isn't the best solution. You can get the same
effect by just sticking something in a comment line a few lines into
the ebuild in a fixed position.
No you can't. It doesn't work with existing package managers,
Agreed. This would require some delay in implementation and would
require users to have some minimal package manager version to handle
major changes in a repository.
> and it
doesn't let you change name or version rules.
Neither does putting the EAPI in the filename as far as I can tell. It
isn't like you want to have ebuild filenames like:
foo-1.1.ebuild-\{EAPI\=1\ \;\ if\ \[\[\ \$PV\ =\ 2.6\ \]\]\ \;\ then\
EAPI\=2\ \;\ fi\}
Putting the EAPI in the filename forces it to be a rigid constant for
the purposes of determining how to parse the file. Putting the EAPI in
a comment line does the same. Both allow for dynamic manipulation of
the variable at a later stage of parsing, but this is after the package
manager has committed to sourcing the file in some particular manner.
If anything you get more flexibility putting it inside the file since at
least you can make it very long without clogging up command lines.
