Re: [gentoo-dev] RFC: Place of EAPI variable in ebuild

[Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>]

[-- Attachment #1: Type: text/plain, Size: 983 bytes --]

On Sun, 11 Nov 2007 21:21:30 +0200
Petteri Räty <betelgeuse@gentoo.org> wrote:
> > Neither EAPI 0 nor EAPI 1 provide any mechanism for an ebuild to
> > 'die' at global scope. There's simply no way for eclasses to
> > complain that they're being misused.
> 
> Well nothing formal but the ebuild developer should pick up ewarn/echo
> /whatever messages coming from global scope. That's what we have in
> debug.eclass atm.

Past experience has shown that those messages will end up being seen by
end users and not being picked up by developers. People changing
eclasses generally don't force a metadata generation for every package
that uses the eclass.

I suspect that for existing eclasses, the safest way to proceed is to
make a new eclass and move common code into a third eclass. So you'd
have foo.eclass doing EAPI 0 specific stuff and inheriting foo-common,
and foo-eapi1.eclass doing EAPI 1 specific stuff and inheriting
foo-common.

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]