From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35621@debbugs.gnu.org,
Vagrant Cascadian <vagrant@reproducible-builds.org>
Subject: bug#35621: Simplify comparing guix challenge results
Date: Wed, 08 May 2019 22:28:46 +0200 [thread overview]
Message-ID: <87zhnwd729.fsf@elephly.net> (raw)
In-Reply-To: <87o94dw10g.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Hi!
>
> Vagrant Cascadian <vagrant@reproducible-builds.org> skribis:
>
>> What about an argument to "guix challenge" that handles the downloading
>> and unpacking to a temporary directory, and possibly another that also
>> runs a comparison tool against the results. Maybe something like:
>>
>> $ guix challenge --download-differences
>> /tmp/git-XXXXX/SUBSTITTE-X/...-git-2.5.0
>> /tmp/git-XXXXX/SUBSTITUTE-Y/...-git-2.5.0
>> /gnu/store/...-git-2.5.0
>>
>> Downloads and unpacks the substitutes, and outputs the resulting
>> directories.
>>
>>
>> $ guix challenge --download-differences --compare-with="diffoscope ..."
>>
>> This would do the above, plus run diffoscope on the directories
>> ... though I think diffoscope can only compare between two things at a
>> time... so that might get difficult if many substitutes return results.
>
> Sounds like a good idea. Perhaps ‘--compare-with’ is actually enough
> (it would also download things), dunno.
I think it’s fine to have just “--compare-with”, which would print the
location of the downloaded things, so you could compare with “echo” if
all you wanted is to get the differences.
--
Ricardo
next prev parent reply other threads:[~2019-05-08 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 18:02 bug#35621: Simplify comparing guix challenge results Vagrant Cascadian
2019-05-08 13:04 ` Ludovic Courtès
2019-05-08 20:28 ` Ricardo Wurmus [this message]
2019-12-09 11:02 ` 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=87zhnwd729.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35621@debbugs.gnu.org \
--cc=ludo@gnu.org \
--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).