From: Vagrant Cascadian <vagrant@debian.org>
To: zimoun <zimon.toutoune@gmail.com>, guix-devel@gnu.org
Subject: Re: guix lint should support overrides
Date: Mon, 05 Sep 2022 10:43:11 -0700 [thread overview]
Message-ID: <87k06hg1jk.fsf@contorta> (raw)
In-Reply-To: <87k06hrcev.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
On 2022-09-05, zimoun wrote:
> On mer., 24 août 2022 at 14:06, Vagrant Cascadian <vagrant@debian.org> wrote:
>
>> Maybe something like:
>>
>> (define-public thispackages
>> (package
>> (name "thispackages"
>> ...
>> (lint-overides
>> (list
>> ;; The upstream name is actually "This Packages", not a typo.
>> "typo in description: 'This Packages' should be 'This Package'"))
>>
>> And then guix lint would hide or ignore things that would otherwise emit
>> the strings listed in lint-overrides ... or something like that. Maybe
>> exact match, maybe get into a little pattern matching, not
>> sure. Implementation is not my strong point here. :)
>
> Well, it is possible to turn off one specific checker for one package;
> using the ’properties’ field. However, this “overides” requires more
> work. :-)
Though a single checker may check multiple things, and only get some of
them "wrong"; seems it would be worth having granularity for individual
checks.
> Basically, the wish is for description and synopsis and mainly for typo,
> right?
No, it seems odd to me to restrict this to particular categories of
checks. I would say any specific lint check might have cases where it is
not practical to fix the lint check, yet is not appropriate for a
particular package.
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-09-05 17:44 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
2022-08-24 21:06 ` Vagrant Cascadian
2022-09-05 16:52 ` zimoun
2022-09-05 17:43 ` Vagrant Cascadian [this message]
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=87k06hg1jk.fsf@contorta \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.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.