Re: [gentoo-dev] rfc: calling all eclass phase functions by default

[Michał Górny]

Dnia 2014-08-17, o godz. 10:32:14
Kent Fredric <kentfredric@×××××.com> napisał(a):

> So if you could sculpt it to be broader by default and have less scope for
> developer error, that'd be an improvement.
>
> --- code start --
> ECLASS_EXCLUDE="foo_src_unpack bar_src_unpack"
> inherit foo bar baz
>
>
> --- code end ---
>
> here, src_unpack would be baz_src_unpack *regardless* of composition order
> because "foo" and "bar" were barred from being used, and baz took
> precedence as a result.

Wow, so you suggest replacing a solution where you have to re-declare
all the phases with one in which you have to opt-out of all phases of
all eclasses...

This thread spreads more great ideas every minute. Soon enough, we will
ban eclasses and require every ebuild to write everything inline just
to be sure. Preferably using kernel calls from assembly to avoid as much
middleware as possible, and make ebuilds as verbose as possible.

-- 
Best regards,
Michał Górny