all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Christopher Baines <mail@cbaines.net>, 59078@debbugs.gnu.org
Subject: [bug#59078] [PATCH] lint: Split the derivation lint checker by system.
Date: Fri, 27 Jan 2023 18:48:19 +0100	[thread overview]
Message-ID: <875ycroom4.fsf_-_@gmail.com> (raw)
In-Reply-To: <86r0y4io7q.fsf@gmail.com> (zimoun's message of "Tue, 15 Nov 2022 10:03:37 +0100")

Hi,

On mar., 15 nov. 2022 at 10:03, zimoun <zimon.toutoune@gmail.com> wrote:
> On Mon, 14 Nov 2022 at 13:51, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> I meant that it’s important to have a single ‘derivation’ checker that
>> checks derivations for all the supported systems.  Packagers should be
>> able to run ‘guix lint -c derivation PKG’ and be confident that it’s
>> fine for all systems.
>
> The CLI invokation is unrelated to the invoked checkers, no?  As Chris
> is proposing, it seems being worth to group some checkers.  For
> instance, we already have the option ’-n, --no-network’ which does that
> but probably at the wrong level.
>
> Maybe we could have another command line option,
>
>     guix lint --group=no-network
>     guix lint --group=derivation
>     guix lint --group=no-network,derivation

What about this?


Cheers,
simon




  reply	other threads:[~2023-01-27 18:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06 13:55 [bug#59078] [PATCH] lint: Split the derivation lint checker by system Christopher Baines
2022-11-07 17:37 ` Christopher Baines
2022-11-11 21:57 ` Ludovic Courtès
2022-11-13 17:27   ` Christopher Baines
2022-11-14 12:51     ` Ludovic Courtès
2022-11-15  8:35       ` Christopher Baines
2022-11-17 17:22         ` Ludovic Courtès
2022-11-15  9:03       ` zimoun
2023-01-27 17:48         ` Simon Tournier [this message]
2023-01-31 16:33           ` Ludovic Courtès
2023-02-01  9:47             ` zimoun

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=875ycroom4.fsf_-_@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=59078@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@cbaines.net \
    /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.