On 9/11/14 12:20 AM, Michał Górny wrote:
> I would like the post-install QA checks to be modularized, standardized
> and extensible. For a start, I've split most of the function into
> install-qa-check.d/ scripts in Portage and made install_qa_check()
> function run them [1]. However, that's just a start.
>
> 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.I see no downsides of this, so +1, and thanks for doing this! I'd let others comment on the implementation details, as I'm not very familiar with bash trickyness, portage and existing checks. Paweł
signature.asc
Description: OpenPGP digital signature
