all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: zimoun <zimon.toutoune@gmail.com>,
	Vagrant Cascadian <vagrant@debian.org>,
	guix-devel@gnu.org
Subject: Re: guix lint should support overrides
Date: Wed, 24 Aug 2022 22:47:01 +0200	[thread overview]
Message-ID: <55c42de4-6aff-1b57-2aa7-b63bf92ce344@telenet.be> (raw)
In-Reply-To: <87h722xdvo.fsf@gmail.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 1481 bytes --]


On 24-08-2022 10:08, zimoun wrote:
> Hi Vagrant,
>
> On Tue, 23 Aug 2022 at 15:22, Vagrant Cascadian<vagrant@debian.org>  wrote:
>
>> But, because there is no way to silence a particular inappropriate
>> suggestion from guix lint, it becomes noise, and each person evaluating
>> the results of the package in the future then needs to take time to
>> figure out if guix lint is wrong, or something should be changed.
> Do you have some packages as example?  In order to be concrete about the
> false-positive and how to programatically fix them.
>
> For instance, do you mean exclude on specific checker for one specific
> package?  Or teach one specific checker for one specific package in
> order to avoid an error specific to this package running this specific
> checker?

Myself (not Vagrant) I was thinking of the gnu-description linter.

IIRC, there was some package where I proposed to modify the description 
a little to be more informative and fit better in Guix, but then the 
gnu-description proposed to use the upstream description. Consequently, 
it was decided to use the original, IMO worse, description.

Unfortunately I cannot find the relevant e-mails anymore.

This was a true positive, not a false positive, but I think it would 
have been useful to silence the linter there anyway.

At least for these kind of cases, I would go for a package property 
(properties '((silence-linters gnu-description))).

Greetings,
Maxime.


[-- Attachment #1.1.1.2: Type: text/html, Size: 2183 bytes --]

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2022-08-24 21:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 22:22 guix lint should support overrides Vagrant Cascadian
2022-08-24  8:08 ` zimoun
2022-08-24 20:47   ` Maxime Devos [this message]
2022-09-02 13:40     ` Ludovic Courtès
2022-08-24 21:06   ` Vagrant Cascadian
2022-09-05 16:52     ` zimoun
2022-09-05 17:43       ` Vagrant Cascadian
2022-08-25 11:31   ` Efraim Flashner
2022-09-02 16:28 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.

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=55c42de4-6aff-1b57-2aa7-b63bf92ce344@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=guix-devel@gnu.org \
    --cc=vagrant@debian.org \
    --cc=zimon.toutoune@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.