unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: Vagrant Cascadian <vagrant@debian.org>, guix-devel@gnu.org
Subject: Re: Preservation of Guix report 2022-01-16
Date: Wed, 19 Jan 2022 11:44:35 +0100	[thread overview]
Message-ID: <87czkoatt8.fsf@gnu.org> (raw)
In-Reply-To: <875yqg96lr.fsf@ngyro.com> (Timothy Sample's message of "Tue, 18 Jan 2022 14:38:56 -0500")

Hi,

Timothy Sample <samplet@ngyro.com> skribis:

> One way to handle things like partial checkouts is to revisit storing
> SWHIDs with our origins.  If you have the directory ID, you can just
> download the directory from SWH without worrying about SVN at all.  It
> would also give us an easy way to handle Bazaar and CVS (which are under
> development at SWH).

That sounds by far the easiest and most robust solution.

The downside is that we’d be storing both the nar hash and the SWHID.
We could arrange so that the daemon checks both hashes when both are
provided.

The more we make progress, the more it seems we won’t be able to avoid
storing multiple hashes.

Thanks,
Ludo’.


  reply	other threads:[~2022-01-19 10:54 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 [this message]
2022-01-20  9:35         ` zimoun
2022-01-24 15:17           ` 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=87czkoatt8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=samplet@ngyro.com \
    --cc=vagrant@debian.org \
    /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).