From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org, "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: Mon, 1 Oct 2018 09:26:18 -0700 [thread overview]
Message-ID: <c245e9c1-ee6d-f318-027e-eca694294417@gentoo.org> (raw)
In-Reply-To: <1538408896.1095.8.camel@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 1304 bytes --]
On 10/01/2018 08:48 AM, Michał Górny wrote:
> On Mon, 2018-10-01 at 08:19 -0700, Zac Medico wrote:
>> I have created a patch that will allow ebuilds to whitelist directories
>> by setting a QA_INSTALL_PATHS variable [3], however @mgorny said:
>
> @mgorny was seriously concerned about trigger-happy patch authors who
> find it urgent to silence QA warnings without even bothering to properly
> discuss the problem.
Discussion takes time, and I'm a very busy person, sorry about that.
Anyway, eventually we are forced to discuss those issues that really matter.
> And is continuously concerned about people who
> want something but don't bother starting the discussion, and instead
> rely on somebody else to start the discussion, even without having
> the appropriate knowledge on what the problem is in the first place.
> In other words, this is something that should be discussed on a case-by-
> case basis. Not the usual Gentoo thing of 'I don't like this QA
> warning, let's silence it quickly and go on ignoring everyone, whether
> my package is broken or not'.
Maybe we should implement a policy requiring gentoo-dev mailing list
proposals for QA_INSTALL_PATHS usage in gentoo ebuilds (similar to the
policy for news items and eclass changes)?
--
Thanks,
Zac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2018-10-01 16:26 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 [this message]
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
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=c245e9c1-ee6d-f318-027e-eca694294417@gentoo.org \
--to=zmedico@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