| 1 |
On 9/11/14 12:20 AM, Michał Górny wrote: |
| 2 |
> I would like the post-install QA checks to be modularized, standardized |
| 3 |
> and extensible. For a start, I've split most of the function into |
| 4 |
> install-qa-check.d/ scripts in Portage and made install_qa_check() |
| 5 |
> function run them [1]. However, that's just a start. |
| 6 |
> |
| 7 |
> I would like to have install-qa-check.d in three main places: |
| 8 |
> |
| 9 |
> 1. /usr/lib/portage/install-qa-check.d (or alike) for scripts |
| 10 |
> installed by Portage and other packages, |
| 11 |
> |
| 12 |
> 2. /etc/portage/install-qa-check.d for extra scripts installed |
| 13 |
> by sysadmin, |
| 14 |
> |
| 15 |
> 3. ${repo}/metadata/install-qa-check.d for repository-specific |
| 16 |
> QA checks. |
| 17 |
> |
| 18 |
> The rationale for (3) is quite simple: many of the modern QA checks are |
| 19 |
> results of policies specific to Gentoo tree and the eclasses in it -- |
| 20 |
> like my recent bash-completion checks (still in review queue). Keeping |
| 21 |
> them in Portage is cumbersome, and has some code duplication factor. |
| 22 |
|
| 23 |
I see no downsides of this, so +1, and thanks for doing this! |
| 24 |
|
| 25 |
I'd let others comment on the implementation details, as I'm not very |
| 26 |
familiar with bash trickyness, portage and existing checks. |
| 27 |
|
| 28 |
Paweł |
Archives