From: Herman Rimm via Guix-patches via <guix-patches@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Josselin Poiret <dev@jpoiret.xyz>,
Simon Tournier <zimon.toutoune@gmail.com>,
Mathieu Othacehe <othacehe@gnu.org>,
Tobias Geerinckx-Rice <me@tobias.gr>,
Florian Pelz <pelzflorian@pelzflorian.de>,
Ricardo Wurmus <rekado@elephly.net>,
Christopher Baines <guix@cbaines.net>,
70499@debbugs.gnu.org
Subject: [bug#70499] [PATCH v2 0/3] Lint package order.
Date: Thu, 4 Jul 2024 22:26:37 +0200 [thread overview]
Message-ID: <geyrevz7sg7kjfdnbyzkdhlczyltsrkohwrgf2bf2octansihq@fzxilgrdtq3s> (raw)
In-Reply-To: <87a5ke0yve.fsf@gnu.org>
Hello,
On Sat, May 25, 2024 at 04:06:45PM +0200, Ludovic Courtès wrote:
> > However the alphabetical order lint warnings only appear once another
> > type of lint warning is emitted, or when end of file is reached and
> > linting finishes. So if few checkers are enabled, it takes a few seconds
> > before anything is output for large module files, like 'crates-io.scm'.
> > Can this be fixed easily?
>
> I’m not sure I understand. The alpabetical checker is part of another
> patch set, right? (I know I’ve seen it, but I’m afraid I’ve lost track
> of it. :-))
>
> Anyway, we can and should discuss ‘--whole-file’ independently of the
> alphabetical-order checker.
I added the '--alphabetical-sort' option to guix style in [bug#70800].
For guix lint, the alphabetical checker is added in [PATCH 3/3]. It
runs only when '--whole-file' is specified. It cannot be toggled with
-c or -x because it is not a normal checker, because run-checkers only
runs on a single package at a time. It could be a normal checker if
given a package, the preceding package can be retrieved. It could be
stored as a parameter. How would you get the preceding package?
> > guix: Move ‘package-location<?’ to (guix packages).
> > ui: Make 'user-module' parameter of 'load*' optional.
> > scripts: lint: Add 'whole-file' option with ordering lint.
>
> This LGTM modulo minor issues:
>
> • The second patch looks unrelated to ‘--whole-file’, I’d drop it from
> this series.
I use load* on the specified file(s). I could instead add a --modules=
MODULE1,MODULE2... option to be used with -L when necessary.
Cheers,
Herman
prev parent reply other threads:[~2024-07-04 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 17:59 [bug#70499] [PATCH] utils: Add find-unordered-packages procedure Herman Rimm via Guix-patches via
2024-05-01 10:30 ` Ludovic Courtès
2024-05-05 17:25 ` [bug#70499] [PATCH v2 0/3] Lint package order Herman Rimm via Guix-patches via
2024-05-05 17:25 ` [bug#70499] [PATCH v2 1/3] guix: Move ‘package-location<?’ to (guix packages) Herman Rimm via Guix-patches via
2024-05-05 17:25 ` [bug#70499] [PATCH v2 2/3] ui: Make 'user-module' parameter of 'load*' optional Herman Rimm via Guix-patches via
2024-05-05 17:25 ` [bug#70499] [PATCH v2 3/3] scripts: lint: Add 'whole-file' option with ordering lint Herman Rimm via Guix-patches via
2024-05-25 14:06 ` [bug#70499] [PATCH v2 0/3] Lint package order Ludovic Courtès
2024-07-04 20:26 ` Herman Rimm via Guix-patches via [this message]
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=geyrevz7sg7kjfdnbyzkdhlczyltsrkohwrgf2bf2octansihq@fzxilgrdtq3s \
--to=guix-patches@gnu.org \
--cc=70499@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=guix@cbaines.net \
--cc=herman@rimm.ee \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=pelzflorian@pelzflorian.de \
--cc=rekado@elephly.net \
--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).