public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-dev] RFC: Portage QA check for FHS/Gentoo policy paths, for top-level dirs and /usr/share/doc
  @ 2018-10-02  7:46 99% ` Andrew Savchenko
  0 siblings, 0 replies; 1+ results
From: Andrew Savchenko @ 2018-10-02  7:46 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]

On Mon, 1 Oct 2018 08:19:29 -0700 Zac Medico 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).

Sometimes documentation contains files used at run-time by the
application. Since application is usually not aware of Gentoo
specific revision numbers it is reasonable to install docs in
${PN}-${PV}. Such checks *must* be overrideable.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
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-02  7:46 99% ` Andrew Savchenko

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox