From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Timothy Sample <samplet@ngyro.com>,
Guix Devel <guix-devel@gnu.org>,
guix-science@gnu.org
Subject: Re: Software Heritage fifth anniversary event
Date: Thu, 02 Dec 2021 16:02:49 +0100 [thread overview]
Message-ID: <87lf13vyli.fsf@inria.fr> (raw)
In-Reply-To: <CAJ3okZ3RoK3_ziWVE5TqF+uRvbpsY-Dgqy4zawjoyv3L9N-Dfw@mail.gmail.com> (zimoun's message of "Thu, 2 Dec 2021 14:17:39 +0100")
Hello!
zimoun <zimon.toutoune@gmail.com> skribis:
>> > • bit-for-bit archival: there’s a tension between making SWH a
>> > “canonical” representation of VCS repos and making it a faithful,
>> > bit-for-bit identical copy of the original, and there are different
>> > opinions in the team here; our use case pretty much requires
>> > bit-for-bit copies, and fortunately this is what SWH is giving us in
>> > practice for Git repos, so checkout authentication (for example)
>> > should work even when fetching Guix from SWH.
>
> The main issue is the lookup. Non bit-for-bit archival implies that
> people store a SWH lookup key (swhid I guess) at ingestion time,
> otherwise it becomes nearly impossible to find back. To me, the
> tension is in the meaning of preservation of source code, i.e.,
> between archiving for reading or archiving for compiling.
Exactly, I guess that’s the big difference. Also: allowing archived
content to be authenticated by third parties vs. having to trust SWH.
> In the case of compilation, all the lookup must be automated and so
> non bit-for-bit archival means: make swhid THE standard for
> serialization; somehow replacing all the other checksums.
Yes, but even if that eventually happens, it’s going to take time.
Ludo’.
next prev parent reply other threads:[~2021-12-02 15:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 9:41 Software Heritage fifth anniversary event Ludovic Courtès
2021-12-01 18:04 ` Timothy Sample
2021-12-02 8:59 ` Ludovic Courtès
2021-12-02 13:17 ` zimoun
2021-12-02 14:04 ` Timothy Sample
2021-12-02 15:49 ` zimoun
2021-12-02 18:04 ` Ludovic Courtès
2021-12-02 15:02 ` Ludovic Courtès [this message]
2021-12-03 3:58 ` Maxim Cournoyer
2021-12-03 11:01 ` Ludovic Courtès
2021-12-05 5:10 ` Maxim Cournoyer
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=87lf13vyli.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=guix-devel@gnu.org \
--cc=guix-science@gnu.org \
--cc=samplet@ngyro.com \
--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.
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).