From: "Ludovic Courtès" <ludo@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 63263@debbugs.gnu.org
Subject: [bug#63263] [PATCH] gexp: Stop generating unreadable builder scripts.
Date: Fri, 05 May 2023 23:45:44 +0200 [thread overview]
Message-ID: <87ild6mozb.fsf_-_@gnu.org> (raw)
In-Reply-To: <875y98nryn.fsf@cbaines.net> (Christopher Baines's message of "Thu, 04 May 2023 13:57:38 +0100")
Hello!
Christopher Baines <mail@cbaines.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> How about a linter instead, with the understanding that use of sexps in
>> packages is vanishing? Perhaps coupled with a ‘guix style’ automatic
>> rewriter.
>
> A linter might be helpful, but I'm not sure it'll help that much.
Yeah.
Another option is ‘guix style -S arguments’:
<https://issues.guix.gnu.org/63320>. Not an immediate fix, but a tool
that would let us move away more quickly from a situation that’s prone
to this kind of error.
[...]
> I guess my perspective on this is more from the operation of the guix
> data service, which is carefully computing and storing all of these
> broken derivations (and there's a lot, like 10,000+ per revision at the
> moment, since they change every time you compute them).
Woow, that’s a lot! Could you send a sample of that list, for one
system type, to get an idea of what’s going on?
Thanks,
Ludo’.
next prev parent reply other threads:[~2023-05-05 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 11:24 [bug#63263] [PATCH] gexp: Stop generating unreadable builder scripts Christopher Baines
2023-05-04 12:47 ` Ludovic Courtès
2023-05-04 12:57 ` Christopher Baines
2023-05-04 19:14 ` Josselin Poiret via Guix-patches via
2023-05-06 8:05 ` Christopher Baines
2023-05-05 21:45 ` Ludovic Courtès [this message]
2023-05-06 7:39 ` Christopher Baines
2023-05-10 15:22 ` Ludovic Courtès
2023-05-10 16:02 ` Christopher Baines
2023-09-01 14:16 ` Maxim Cournoyer
2023-09-02 10:36 ` bug#63263: " Christopher Baines
2023-09-03 14:54 ` [bug#63263] " Maxim Cournoyer
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=87ild6mozb.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=63263@debbugs.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.