From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel@gnu.org
Subject: Re: Preservation of Guix report 2022-01-16
Date: Mon, 24 Jan 2022 16:17:26 +0100 [thread overview]
Message-ID: <871r0xtb7d.fsf@gnu.org> (raw)
In-Reply-To: <864k5yoim0.fsf@gmail.com> (zimoun's message of "Thu, 20 Jan 2022 10:35:03 +0100")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
>> The more we make progress, the more it seems we won’t be able to avoid
>> storing multiple hashes.
>
> Yes, it appears to me unavoidable. The question is where store such
> hashes? At the origin level? At the package level via ’properties’?
> Using an external service? As Disarchive database? Other?
I was thinking <origin> could accept several hashes.
> From my point of view, the bridge between all the hashes should be done
> by SWH itself. They promote their ’swhid’ which is far less common than
> Git hashes, for instance. It would make sense, at least to me, that
> they would provide various maps using different keys. They already
> somehow provide the map Git+Sha1 to swid, they could also provide
> NAR+Sha256 to swhid and maybe other serializers checksum to swhid. The
> world existed before swhid. ;-)
In principle, sure, it would be nice if SWH could map from one hash
flavor to another.
In practice, I can understand why they wouldn’t want to compute
nar/sha256 or some other underground flavor for all the archived source.
I think we have to do something on our side. We could “upgrade”
<origin>, ‘guix-daemon’, and ‘guix publish’ so they can usefully handle
multiple hashes. That’d be a long-term effort.
Now, an external “hash mapping service” has its appeal: it could be put
to work right away. Tricky!
Ludo’.
prev parent reply other threads:[~2022-01-24 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 19:51 Preservation of Guix report 2022-01-16 Timothy Sample
2022-01-18 15:28 ` Ludovic Courtès
2022-01-18 18:16 ` Vagrant Cascadian
2022-01-18 19:38 ` Timothy Sample
2022-01-19 10:44 ` Ludovic Courtès
2022-01-20 9:35 ` zimoun
2022-01-24 15:17 ` Ludovic Courtès [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=871r0xtb7d.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.org \
--cc=zimon.toutoune@gmail.com \
/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.