Gentoo Archives: gentoo-dev

From: Andrew Savchenko <bircoph@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] RFC: Portage QA check for FHS/Gentoo policy paths, for top-level dirs and /usr/share/doc
Date: Tue, 02 Oct 2018 07:47:01
Message-Id: 20181002104638.c4f7b05522c40b6759622aa6@gentoo.org
In Reply to: [gentoo-dev] RFC: Portage QA check for FHS/Gentoo policy paths, for top-level dirs and /usr/share/doc by Zac Medico
1 On Mon, 1 Oct 2018 08:19:29 -0700 Zac Medico wrote:
2 > Hi all,
3 >
4 > The ~arch version of portage hs a new QA check that reports installation
5 > of files outside of directories that have been whitelisted [1]. The
6 > current whitelist includes:
7 >
8 > directories common to / and /usr
9 > ================================
10 > bin lib lib32 lib64 libx32 sbin
11 >
12 > top level directories
13 > ================================
14 > boot dev etc opt srv usr var
15 >
16 > /usr level directories
17 > ================================
18 > include libexec share src
19 >
20 > /usr/share/doc level directories
21 > ================================
22 > /usr/share/doc/${PF}
23 >
24 > The first bug report [2] is for qt-core, which installs documentation
25 > into /usr/share/doc/${PN}-${PV} instead of /usr/share/doc/${PF} (${PF}
26 > includes ebuild revision such as -r1, -r2, and so on).
27
28 Sometimes documentation contains files used at run-time by the
29 application. Since application is usually not aware of Gentoo
30 specific revision numbers it is reasonable to install docs in
31 ${PN}-${PV}. Such checks *must* be overrideable.
32
33 Best regards,
34 Andrew Savchenko