all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 33540@debbugs.gnu.org
Subject: [bug#33540] [PATCH 2/3] gnu: Add lttoolbox.
Date: Mon, 03 Dec 2018 10:36:10 +0100	[thread overview]
Message-ID: <87ftvf7y0l.fsf@gnu.org> (raw)
In-Reply-To: <cu74lbvt62t.fsf@systemreboot.net> (Arun Isaac's message of "Mon, 03 Dec 2018 13:06:26 +0530")

Arun Isaac <arunisaac@systemreboot.net> skribis:

>>> +     (origin
>>> +       (method url-fetch)
>>> +       (uri (string-append
>>> +             "https://github.com/apertium/lttoolbox/releases/download/v"
>>> +             version "/lttoolbox-" version ".tar.gz"))
>>
>> Instead of relying on generated tarballs like this one whose content may
>> change over time, we’re now switching to using ‘git-fetch’.  Could you
>> change this one accordingly?
>
> I don't think
> https://github.com/apertium/apertium/releases/download/v3.5.2/apertium-3.5.2.tar.gz
> is an autogenerated tarball. That is at
> https://github.com/apertium/apertium/archive/v3.5.2.tar.gz . Should I
> still switch to using git-fetch?
>
> That said, I tried building lttoolbox again now, and the hash does seem
> to have changed. I don't understand what's going on.

Ouch.  Indeed GitHub has an “asset” feature that some projects use,
which allows them to upload tarballs.  You could use that (esp. since
the project uses the Autotools), except if it turns out to be modified
in place too often…

Ludo’.

  reply	other threads:[~2018-12-03  9:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-28 16:55 [bug#33540] [PATCH 0/3] Add apertium Arun Isaac
2018-11-30  0:22 ` swedebugia
2018-11-30  7:12   ` Arun Isaac
2018-11-30  7:16 ` [bug#33540] [PATCH 1/3] gnu: dictionaries: Use license prefix Arun Isaac
2018-11-30  7:16   ` [bug#33540] [PATCH 2/3] gnu: Add lttoolbox Arun Isaac
2018-12-02 22:26     ` Ludovic Courtès
2018-12-03  7:36       ` Arun Isaac
2018-12-03  9:36         ` Ludovic Courtès [this message]
2018-11-30  7:16   ` [bug#33540] [PATCH 3/3] gnu: Add apertium Arun Isaac
2018-12-02 22:28     ` Ludovic Courtès
2018-12-02 22:23   ` [bug#33540] [PATCH 1/3] gnu: dictionaries: Use license prefix Ludovic Courtès
2018-12-03 16:50 ` [bug#33540] [PATCH v2 0/3] Add lttoolbox, apertium Arun Isaac
2018-12-03 16:50   ` [bug#33540] [PATCH v2 1/3] gnu: dictionaries: Use license prefix Arun Isaac
2018-12-03 16:50   ` [bug#33540] [PATCH v2 2/3] gnu: Add lttoolbox Arun Isaac
2018-12-03 16:50   ` [bug#33540] [PATCH v2 3/3] gnu: Add apertium Arun Isaac
2018-12-04  8:36   ` [bug#33540] [PATCH v2 0/3] Add lttoolbox, apertium Ludovic Courtès
2018-12-04 18:41     ` bug#33540: " Arun Isaac

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=87ftvf7y0l.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33540@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    /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.