public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andreas Sturmlechner <asturm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-dev] RFC: Portage QA check for FHS/Gentoo policy paths, for top-level dirs and /usr/share/doc
Date: Sun, 27 Jan 2019 14:58:34 +0100	[thread overview]
Message-ID: <59565022.tOID2UdrHk@tuxk10> (raw)
In-Reply-To: <1538417788.1095.10.camel@gentoo.org>

On Montag, 1. Oktober 2018 20:16:28 CET Michał Górny wrote:
> >  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).
> 
> Yes.  That is why I believe that hardcoding the exception in every
> package is simply wrong.  Wouldn't it be cleaner to account for the path
> in the QA check?

What's the current status of this? I'd like to know if there's going to be a 
whitelist or QA_ var to put into kde5.eclass, if not, I can also simply 
(EAPI-7-)move kde handbook directory out of /usr/share/doc into /usr/share/
kde-doc or similar and be done with it.

Regards,
Andreas





  parent reply	other threads:[~2019-01-27 13:58 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 [this message]
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=59565022.tOID2UdrHk@tuxk10 \
    --to=asturm@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=mgorny@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