From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 56092@debbugs.gnu.org,
Vagrant Cascadian <vagrant@reproducible-builds.org>
Subject: [bug#56092] [PATCH] challenge: Do nothing when passed zero arguments.
Date: Mon, 20 Jun 2022 22:15:52 +0200 [thread overview]
Message-ID: <87a6a76qh3.fsf@gnu.org> (raw)
In-Reply-To: <03ea39543378bc4b40b45f603553b8b6615aa7ec.camel@telenet.be> (Maxime Devos's message of "Mon, 20 Jun 2022 16:48:55 +0200")
Hi,
Maxime Devos <maximedevos@telenet.be> skribis:
> Ludovic Courtès schreef op zo 19-06-2022 om 15:55 [+0200]:
>> Hi!
>>
>> This changes ‘guix challenge’ such that, with no arguments, it does
>> nothing, which is arguably less confusing that the current behavior.
>
> Having "guix challenge" be able to check your entire store for
> reproducibility seemed a nifty feature to me. E.g., it's as good a
> starting point as any to look for which packages need some
> reproducibility fixes.
It seemed to make sense back then, when the store was typically much
smaller. Today it’s no longer a reasonable default as you write.
> I agree that doing the _entire store_ by _default_ is a bit much, but
> I'd like the old behaviour to be still available somewhere (guix
> challenge --all-local-things?)
It can be approximated with ‘guix challenge $(guix gc --list-live)’.
It’s not exactly the same: things not built locally are also included.
But I find that it’s just as useful.
So I’d lean towards not adding an option for that.
WDYT?
Ludo’.
PS: What would be useful is a ‘--manifest’ option—future work!
next prev parent reply other threads:[~2022-06-20 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 13:55 [bug#56092] [PATCH] challenge: Do nothing when passed zero arguments Ludovic Courtès
2022-06-20 14:48 ` Maxime Devos
2022-06-20 20:15 ` Ludovic Courtès [this message]
2022-06-20 20:18 ` Maxime Devos
2022-07-02 23:43 ` bug#56092: " Ludovic Courtès
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=87a6a76qh3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=56092@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=vagrant@reproducible-builds.org \
/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).