[gentoo-dev] RFC: [Future EAPI] Exporting phase funcs from direct inherits only

["Michał Górny" <mgorny@gentoo.org>]

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

Hello,

As some of you may have noticed, lately introduced 'double include
preventions' have caused changes in effective phase functions in a few
ebuilds. Also, often it is undesirable that change in inherits of
an eclass may cause an undesired change of exported functions. To solve
these problems, we are proposing the following:


1. If an ebuild does not provide an explicit phase function, the phase
functions *directly exported* by *directly inherited* eclasses are used
to find a suitable default,

2. Thus, if an eclass inherits another eclass and expects the phase
functions of that eclass to be effective to the ebuild, it needs to
create its own phase function and export it.


This should make the ebuild behavior simpler to understand and saner.
It should also fix the forementioned issues, and allow us to make
the 'source eclasses only once'[1] proposal simpler.

[1]:https://bugs.gentoo.org/show_bug.cgi?id=422533

-- 
Best regards,
Michał Górny

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