From: Zac Medico <zmedico@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] RFC: Portage QA check for FHS/Gentoo policy paths, for top-level dirs and /usr/share/doc
Date: Mon, 1 Oct 2018 08:19:29 -0700 [thread overview]
Message-ID: <1df93cd0-b3e7-56cf-3a29-bfaed2069e02@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1294 bytes --]
Hi all,
The ~arch version of portage hs a new QA check that reports installation
of files outside of directories that have been whitelisted [1]. The
current whitelist includes:
directories common to / and /usr
================================
bin lib lib32 lib64 libx32 sbin
top level directories
================================
boot dev etc opt srv usr var
/usr level directories
================================
include libexec share src
/usr/share/doc level directories
================================
/usr/share/doc/${PF}
The first bug report [2] is for qt-core, which installs documentation
into /usr/share/doc/${PN}-${PV} instead of /usr/share/doc/${PF} (${PF}
includes ebuild revision such as -r1, -r2, and so on).
I have created a patch that will allow ebuilds to whitelist directories
by setting a QA_INSTALL_PATHS variable [3], however @mgorny said:
On Mon, Oct 1, 2018 at 12:34 AM Michał Górny <mgorny@gentoo.org> wrote:
> QA NAK on this. The purpose of QA checks is not for ebuilds to
> officially override them because histerical raisins.
[1]
https://gitweb.gentoo.org/proj/portage.git/commit/?id=d5f97eaa464736a454c8ad410f4acd4fccdf2324
[2] https://bugs.gentoo.org/667280
[3] https://bugs.gentoo.org/667378
--
Thanks,
Zac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next reply other threads:[~2018-10-01 15:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 15:19 Zac Medico [this message]
2018-10-01 15:34 ` [gentoo-dev] RFC: Portage QA check for FHS/Gentoo policy paths, for top-level dirs and /usr/share/doc 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
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=1df93cd0-b3e7-56cf-3a29-bfaed2069e02@gentoo.org \
--to=zmedico@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