all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: diffoscope: Update to version 115-1.7f3416f.
Date: Thu, 30 May 2019 17:21:38 -0700	[thread overview]
Message-ID: <87lfyn323x.fsf@yucca> (raw)
In-Reply-To: <87sgsvplgx.fsf@nckx>

[-- Attachment #1: Type: text/plain, Size: 954 bytes --]

On 2019-05-31, Tobias Geerinckx-Rice wrote:
> Vagrant,
>
> guix-commits@gnu.org wrote:
>> gnu: diffoscope: Update to version 115-1.7f3416f.
>
> I wondered why this was updated to a git revision instead of the 
> 115 release tag, and found:

Realized I should have included a comment explaining why that commit was
used right after I pushed...


>     Commit 7f3416ff
>     Committed by Vagrant Cascadian 6 days ago
>
>     Add support for known external tools on GNU Guix.[1]
>
> Nice.  Thank you!

Especially since guix's diffoscope doesn't install *all* of the tools
needed, that seemed like an important feature to get working, as it
allows you to:

  diffoscope --list-missing-tools guix

And it will suggest packages you might want to install.

Though I did wonder if there shouldn't be a
diffoscope-with-the-kitchen-sink variant that does pull in everything
available.

Happy diffoscoping!

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      reply	other threads:[~2019-05-31  0:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190530230533.32063.56999@vcs0.savannah.gnu.org>
     [not found] ` <20190530230536.166A220996@vcs0.savannah.gnu.org>
2019-05-30 23:32   ` 01/01: gnu: diffoscope: Update to version 115-1.7f3416f Tobias Geerinckx-Rice
2019-05-31  0:21     ` Vagrant Cascadian [this message]

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=87lfyn323x.fsf@yucca \
    --to=vagrant@reproducible-builds.org \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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.