From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: zimoun <zimon.toutoune@gmail.com>,
Vagrant Cascadian <vagrant@debian.org>,
guix-devel@gnu.org
Subject: Re: guix lint should support overrides
Date: Fri, 02 Sep 2022 15:40:10 +0200 [thread overview]
Message-ID: <875yi5x5c5.fsf@gnu.org> (raw)
In-Reply-To: <55c42de4-6aff-1b57-2aa7-b63bf92ce344@telenet.be> (Maxime Devos's message of "Wed, 24 Aug 2022 22:47:01 +0200")
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> 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))).
Yes, properties are the way to go IMO.
Note that there’s already one or two checker-specific properties, such
as ‘lint-hidden-cve’. We could add more of that if needed.
A higher-level ‘lint-silenced-checkers’ property like you propose (I
think that’s a better name) would also be welcome.
It’s incidentally a good programming task to get started; who’s in? :-)
Ludo’.
next prev parent reply other threads:[~2022-09-02 13:42 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
2022-09-02 13:40 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yi5x5c5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).