From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: Julien Lepiller <julien@lepiller.eu>, 34449@debbugs.gnu.org
Subject: [bug#34449] [PATCH] gnu: Add trydiffoscope.
Date: Tue, 12 Feb 2019 00:16:42 -0800 [thread overview]
Message-ID: <87r2cda0b9.fsf@ponder> (raw)
In-Reply-To: <70476863-38DA-4DA0-BBA9-82B20B2AB197@lepiller.eu>
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
On 2019-02-12, Julien Lepiller wrote:
> Le 12 février 2019 03:08:36 GMT+01:00, Vagrant Cascadian <vagrant@reproducible-builds.org> a écrit :
>>
>>* gnu/packages/package-management (trydiffoscope): New variable.
...
>>+ (synopsis "Compare files and archives in depth")
>>+ (description
>>+ "This is a minimal diffoscope client that connects to the
>>service:
>>+
>>+https://try.diffoscope.org.
>>+
>>+Diffoscope tries to get to the bottom of what makes files or
>>directories
>>+different. It recursively unpacks archives of many kinds and
>>transforms
>>+various binary formats into more human readable forms to compare them.
>> It can
>>+compare two tarballs, ISO images, or PDFs just as easily.")
>>+ (license license:gpl3+)))
>>+
>> (define-public python-anaconda-client
>> (package
>> (name "python-anaconda-client")
> Iiuc, this is a client to connect to a service that runs diffoscope
> for you. But we already have diffoscope, so what's the point?
Yes, that's the jist of it. The main advantage is that it has a much
smaller dependency chain locally.
I find it useful on some of the not-particularly-fast ARM systems I've
been running GNU Guix, where storage may be limited or slow, and
substitutes may not be available as often, and build times
are... remarkable.
> Also this looks like saass to me, so I think we should refrain from
> adding it to guix.
It is essentially SaaSS. The server-side is at least licensed under the
AGPL, if that mitigates concerns somewhat.
I'm not sure it supports it out of the box yet, but I suspect upstream
would be amenable to patches to make it easy for people to run their own
"diffoscope" services.
> What do you think?
I thought it was useful enough to be worth submitting, though I'd
understand if it's deemed inappropriate for GNU Guix. Still learning the
ropes. :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-02-12 8:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 2:08 [bug#34449] [PATCH] gnu: Add trydiffoscope Vagrant Cascadian
2019-02-12 7:31 ` Julien Lepiller
2019-02-12 8:16 ` Vagrant Cascadian [this message]
2019-02-12 9:34 ` Julien Lepiller
2019-02-12 20:37 ` Leo Famulari
2019-02-13 8:05 ` Julien Lepiller
2019-02-13 21:43 ` Vagrant Cascadian
2019-02-13 23:58 ` bug#34449: " Leo Famulari
2019-02-14 0:26 ` [bug#34449] " Vagrant Cascadian
2019-02-14 0:32 ` Leo Famulari
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=87r2cda0b9.fsf@ponder \
--to=vagrant@reproducible-builds.org \
--cc=34449@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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.