Re: [gentoo-dev] Early idea: install_qa_check() refactor and 'public API'

[Michał Górny]

Dnia 2014-09-13, o godz. 16:03:31
Jauhien Piatlicki <jauhien@g.o> napisał(a):

> Hi,
>
> 11.09.14 00:20, Michał Górny написав(ла):
> >
> > I would like to have install-qa-check.d in three main places:
> >
> > 1. /usr/lib/portage/install-qa-check.d (or alike) for scripts
> > installed by Portage and other packages,
> >
> > 2. /etc/portage/install-qa-check.d for extra scripts installed
> > by sysadmin,
> >
> > 3. ${repo}/metadata/install-qa-check.d for repository-specific
> > QA checks.
> >
> > The rationale for (3) is quite simple: many of the modern QA checks are
> > results of policies specific to Gentoo tree and the eclasses in it --
> > like my recent bash-completion checks (still in review queue). Keeping
> > them in Portage is cumbersome, and has some code duplication factor.
>
> nice idea, +1 from me.
>
> One question related to (3): am I correct that not only scripts from ${repo}/metadata/install-qa-check.d, but also scripts from the repos that current repo has in masters from metadata/layout.conf will be runned? It means that these scripts will be 'inherited' by repos?

Yes, Portage follows masters looking for scripts. Not exactly inherited
since with current logic two repos can have a script with the same name
and both will be run (however, this may change in the future).

-- 
Best regards,
Michał Górny