From: Sergei Trofimovich <slyfox@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: Mon, 1 Oct 2018 21:04:18 +0100 [thread overview]
Message-ID: <20181001210418.75f712d5@sf> (raw)
In-Reply-To: <1df93cd0-b3e7-56cf-3a29-bfaed2069e02@gentoo.org>
On Mon, 1 Oct 2018 08:19:29 -0700
Zac Medico <zmedico@gentoo.org> wrote:
> 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}
As this will break existing ebuilds I'd suggest guarding it against
next EAPI. Out of top of by head the change will break at least
crossdev outright. At least for two reasons:
1. building a gcc cross-compiler usually refers to $SYSROOT/sys-include.
'git grep sys-include' will show a bunch of ebuilds that create that
symlinks outside the space.
2. cross-building target libc is currently done on the host's emerge
and installs into /usr/$CTARGET/.
I think whitelist would be able to cover these use cases as they are
a function of ${CTARGET} (or $CATEGORY) value.
--
Sergei
next prev parent reply other threads:[~2018-10-01 20:04 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
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 [this message]
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=20181001210418.75f712d5@sf \
--to=slyfox@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