unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: guix-devel@gnu.org
Subject: Re: Custom sha256 updaters ?
Date: Thu, 26 Sep 2024 15:43:44 +0200	[thread overview]
Message-ID: <87tte2msxb.fsf@gnu.org> (raw)
In-Reply-To: <875xqp3ob4.fsf@ngraves.fr> (Nicolas Graves's message of "Sat, 21 Sep 2024 01:20:15 +0200")

Hi,

Nicolas Graves <ngraves@ngraves.fr> skribis:

> Has there already been some discussion about custom hash updaters? I
> have written an import module for libreoffice, and we have access to the
> sha256 hash in for example
>
> https://download.documentfoundation.org/libreoffice/src/24.2.6/libreoffice-24.2.6.2.tar.xz.sha256
>
> which would make it trivial to update without having to download 267MiB
> of data twice.
>
> However, %method-updates doesn't seem to allow such a flexibility for
> now. Maybe a custom field for a function in <upstream-updater> could be
> possible? WDYT?

This hasn’t been discussed before, but allow me to be skeptical.  :-)

First because if you run ‘guix refresh -u’, surely you’ll want to
download the file (and note that it downloads it once, not twice,
because the file goes into the store).

Second because I think we want to encourage packagers to authenticate
source tarballs, and files containing lists of hashes are not helpful
for that.

Does that make sense?

Ludo’.


  reply	other threads:[~2024-09-26 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20 23:20 Custom sha256 updaters ? Nicolas Graves
2024-09-26 13:43 ` Ludovic Courtès [this message]
2024-09-26 14:37   ` Nicolas Graves

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=87tte2msxb.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ngraves@ngraves.fr \
    /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).