Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
Ciaran McCreesh kirjoitti:
> On Sun, 11 Nov 2007 21:01:41 +0200
> Petteri Räty <betelgeuse@g.o> wrote:
>> If we go with this solution then I guess eclasses must check for the
>> EAPI variable and then act accordingly. For example if the ebuild sets
>> EAPI=2 and the eclass is designed for EAPI=1 then it could be made to
>> die in case EAPI 2 is not backwards compatible. The main reason for me
>> asking this it that I plan to make the java eclasses use the EAPI 1
>> features.
>
> 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.
Regards,
Petteri
|
|
