Gentoo Archives: gentoo-dev

From: Georgy Yakovlev <gyakovlev@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [PATCH] metadata/policy.conf: Introduce QA check configuration
Date: Wed, 26 Feb 2020 10:52:46
Message-Id: 20200226025238.7c0f11c11687d736e3c305d1@gentoo.org
In Reply to: [gentoo-dev] [PATCH] metadata/policy.conf: Introduce QA check configuration by "Michał Górny"
1 On Wed, 26 Feb 2020 11:23:49 +0100
2 Michał Górny <mgorny@g.o> wrote:
3
4 > Introduce a new configuration file for assigning QA check significance
5 > levels to PGnnnn policies. Long-term goal is that this will permit
6 > unified configuration of various QA tools, including pkgcheck, repoman
7 > and install-qa-check.d.
8 >
9 > Signed-off-by: Michał Górny <mgorny@g.o>
10 > ---
11 > metadata/policy.conf | 61 ++++++++++++++++++++++++++++++++++++++++++++
12 > 1 file changed, 61 insertions(+)
13 > create mode 100644 metadata/policy.conf
14 >
15 > diff --git a/metadata/policy.conf b/metadata/policy.conf
16 > new file mode 100644
17 > index 000000000000..824598063cc1
18 > --- /dev/null
19 > +++ b/metadata/policy.conf
20 > @@ -0,0 +1,61 @@
21 > +# Copyright 2020 Gentoo Authors
22 > +# Distributed under the terms of the GNU General Public License v2
23 > +
24 > +# The policy section assigns significance levels to various policies.
25 > +# Keys are identifiers from the Policy Guide, values are either
26 > +# 'notice', 'warninging' or 'error'.
27 extra ing here
28 > +#
29 > +# The rule of thumb is that 'error' indicates a serious problem that
30 > +# may cause serious problem to the end users and therefore should block
31 > +# committing / deployment. 'Warning' should be fixed by developer
32 capital W probably should be w
33 > +# but does not need to immediately prevent committing.
34 > +#
35 > +# https://projects.gentoo.org/qa/policy-guide/std-policy-index.html
36 > +
37
38 Looks really interesting.
39 Will overlays be able to define their own policy ?
40 Maybe rename file to metadata/qa-policy.conf ? just policy.conf is ambiguous.
41
42 --
43 Georgy Yakovlev <gyakovlev@g.o>

Replies