From: Andreas Sturmlechner <asturm@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, 01 Oct 2018 19:23:12 +0200 [thread overview]
Message-ID: <2733265.gtnf6FpWjD@tuxbrain> (raw)
In-Reply-To: <1538408896.1095.8.camel@gentoo.org>
On Montag, 1. Oktober 2018 17:48:16 CEST Michał Górny wrote:
> On Mon, 2018-10-01 at 08:19 -0700, Zac Medico wrote:
> > /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).
>
> No, it doesn't. There's no /usr/share/doc/qtcore-5.11.1 on my system.
This is coming from dev-qt/qt-docs. It is a problem because any other package
building QCH API docs with cross-references to Qt API needs to install below
this path, and will generate the same QA warning (currently kde-frameworks/*
does this).
next prev parent reply other threads:[~2018-10-01 17:23 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 [this message]
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=2733265.gtnf6FpWjD@tuxbrain \
--to=asturm@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