From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Portage QA check for FHS/Gentoo policy paths, for top-level dirs and /usr/share/doc
Date: Wed, 3 Oct 2018 14:26:23 -0400 [thread overview]
Message-ID: <545032b4-c3bc-d5cc-6d9e-02db4bdcfc51@gentoo.org> (raw)
In-Reply-To: <c94b237f-6e3a-b52a-2cec-e81519ed850f@gentoo.org>
On 10/03/2018 12:38 PM, Zac Medico wrote:
>
> Until this QA check has adjustable whitelist support, we can consider it
> an unstable work in progress.
Has anyone said why these things need to be in ${PN}-${PV} rather than
${PF}?
If they don't need to be in ${PN}-${PV} in the first place, then the QA
check is just doing exactly what it's supposed to. If, on the other
hand, there's a good reason for something to install docs outside of
${PF}, then we should just fix the check (and our policy) to allow it.
(A whitelist is IMO the wrong approach, the QA check should never report
"correct" things in the first place.)
next prev parent reply other threads:[~2018-10-03 18:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 15:19 [gentoo-dev] RFC: Portage QA check for FHS/Gentoo policy paths, for top-level dirs and /usr/share/doc Zac Medico
2018-10-01 15:34 ` Mike Gilbert
2018-10-01 15:38 ` [gentoo-dev] " Michael Orlitzky
2018-10-01 15:48 ` [gentoo-dev] " Michał Górny
2018-10-01 16:26 ` Zac Medico
2018-10-01 17:23 ` Andreas Sturmlechner
2018-10-01 18:16 ` Michał Górny
2018-10-01 18:23 ` Zac Medico
2018-10-03 16:38 ` Zac Medico
2018-10-03 18:26 ` Michael Orlitzky [this message]
2018-10-03 18:29 ` Andreas Sturmlechner
2018-10-03 20:10 ` Michał Górny
2019-01-27 13:58 ` Andreas Sturmlechner
2018-10-01 20:04 ` Sergei Trofimovich
2018-10-01 20:48 ` Zac Medico
2018-10-01 21:45 ` Sergei Trofimovich
2018-10-02 7:46 ` Andrew Savchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545032b4-c3bc-d5cc-6d9e-02db4bdcfc51@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox