Re: [gentoo-dev] RFC: Portage QA check for FHS/Gentoo policy paths, for top-level dirs and /usr/share/doc

[Mike Gilbert <floppym@gentoo.org>]

On Mon, Oct 1, 2018 at 11:19 AM 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}
>
> 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.

I don't think QA has the final word on features that are added to the
package manager. They can prevent abuse of those features by ebuilds
in the repository, however.

Personally, I think compatibility with historical code is a perfectly
valid reason to make an exception here.