Gentoo Archives: gentoo-dev

From: Jauhien Piatlicki <jauhien@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Early idea: install_qa_check() refactor and 'public API'
Date: Sat, 13 Sep 2014 14:03:53
Message-Id: 54144EB3.1020402@gentoo.org
In Reply to: [gentoo-dev] Early idea: install_qa_check() refactor and 'public API' by "Michał Górny"
1 Hi,
2
3 11.09.14 00:20, Michał Górny написав(ла):
4 >
5 > I would like to have install-qa-check.d in three main places:
6 >
7 > 1. /usr/lib/portage/install-qa-check.d (or alike) for scripts
8 > installed by Portage and other packages,
9 >
10 > 2. /etc/portage/install-qa-check.d for extra scripts installed
11 > by sysadmin,
12 >
13 > 3. ${repo}/metadata/install-qa-check.d for repository-specific
14 > QA checks.
15 >
16 > The rationale for (3) is quite simple: many of the modern QA checks are
17 > results of policies specific to Gentoo tree and the eclasses in it --
18 > like my recent bash-completion checks (still in review queue). Keeping
19 > them in Portage is cumbersome, and has some code duplication factor.
20
21 nice idea, +1 from me.
22
23 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?
24
25 --
26 Regards,
27 Jauhien

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies