From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Mutable Git tags & Software Heritage
Date: Tue, 09 Nov 2021 17:55:09 +0100 [thread overview]
Message-ID: <87czn9jmky.fsf@gnu.org> (raw)
In-Reply-To: <86ee82jxhw.fsf@gmail.com> (zimoun's message of "Sat, 30 Oct 2021 18:19:55 +0200")
Hello,
zimoun <zimon.toutoune@gmail.com> skribis:
> On Fri, 29 Oct 2021 at 16:12, Ludovic Courtès <ludo@gnu.org> wrote:
[...]
>>> Well, because it is not affordable to switch from the current
>>> tag-address to immutable commit-address for defining packages, in order
>>> to be 100% reliable, any fallback should use Disarchive-DB which stores
>>> the mapping from checksum to swhid; for all kind origins.
>>>
>>> Is it what you have in mind?
>>
>> No, I think we should consider always referring to commits instead of
>> tags. It’s annoying from a readability viewpoint, but it would ensure
>> reproducibility. Even flatpak has this policy. :-)
>
> Ah, IMHO, «it is not affordable to switch from the current tag-address
> to immutable commit-address for defining packages, in order to be 100%
> reliable» :-)
>
> Do you think the switch from tag to commit instead is really doable?
>
> Other said, do you think it should be possible to automatize such task?
With enough effort, anything can be automated. That said, I think it
would be fine to change things incrementally as packages are
added/updated.
> PS: Ah, refer to commit instead of tags could be a RFC. ;-)
Yup! :-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-11-09 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 19:48 Preservation of Guix Report Timothy Sample
2021-10-21 2:04 ` Timothy Sample
2021-10-21 7:39 ` zimoun
2021-10-21 16:26 ` Timothy Sample
2021-10-22 7:58 ` zimoun
2021-10-21 20:47 ` Ludovic Courtès
2021-10-22 7:53 ` zimoun
2021-10-29 14:12 ` Mutable Git tags & Software Heritage Ludovic Courtès
2021-10-30 16:19 ` zimoun
2021-11-09 16:55 ` Ludovic Courtès [this message]
2021-10-22 14:19 ` Preservation of Guix Report Timothy Sample
2021-10-22 17:32 ` Timothy Sample
2021-10-29 14:20 ` Ludovic Courtès
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=87czn9jmky.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.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 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).