On Tue, 11 Dec 2007 20:00:51 -0500
Doug Klima <[EMAIL PROTECTED]> wrote:
> When you could simply have $pkg_manager execute an eclass as 1
> EAPI, another eclass as another and the ebuild as a third EAPI and
> simplify it for the eclass maintenance.
Which doesn't work at all. Simple example would be the introduction of
new phases, e.g. src_configure with EAPI=2:
foo.eclass:
EAPI=2
setup_env {
# do some stuff that differs betwwen EAPI-1 and EAPI-2
}
src_configure {
econf --some-special-eclass-option
}
bar.ebuild:
inherit foo
EAPI=1
setup_env
# no src_* functions defined
Now should the package manager execute src_configure or not? And that's
assuming we actually track all values of EAPI and their origin as well
as the origin of all functions/variables in the current environment.
Or should setup_env be executed with EAPI=1 (as it's called in the
ebuild) or EAPI=2 (as it's defined in the eclass)? There are no real
answers to those problems.
Marius
--
[EMAIL PROTECTED] mailing list
