[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#56092] [PATCH] challenge: Do nothing when passed zero arguments.
From: |
Ludovic Courtès |
Subject: |
[bug#56092] [PATCH] challenge: Do nothing when passed zero arguments. |
Date: |
Mon, 20 Jun 2022 22:15:52 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) |
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!