`multilib-minimal.eclass`'es documentation says [1]: > multilib-minimal should _always_ go last in inherit order! (BTW `multilib-build.eclass`'es doesn't [2]. Should it?) Nobody follows this rule: [3]. Should we add a QA test for this case? --- [1] https://devmanual.gentoo.org/eclass-reference/multilib-minimal.eclass/index.html [2] https://devmanual.gentoo.org/eclass-reference/multilib-build.eclass/index.html [3] https://github.com/search?q=org%3Agentoo+multilib-minimal&type=code
It's just an idea copied from games.eclass. Nowadays we have exported phases much better organized so most of the time there's little risk of another eclass overriding its phase functions.