unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: guix pack file enumerator?
Date: Mon, 14 Dec 2020 10:48:34 +0100	[thread overview]
Message-ID: <87zh2gvhu5.fsf@gnu.org> (raw)
In-Reply-To: <87a6unnsud.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 09 Dec 2020 12:04:26 +0100")

Hi,

Ricardo Wurmus <rekado@elephly.net> skribis:

> I’m unpacking to rsync now, but it’s not great to duplicate files on the
> local disk only to send them over the network.  The ideal workflow for
> me would treat the store on my local machine as the source and the
> remote machine as the target, without any copying from source to source
> in between.
>
> The local-unpack method also requires an empty directory to be
> maintained; it needs to be emptied before the next time we try to unpack
> anything.
>
> Another downside is the creation of the tarball itself.  I don’t need it
> but it’s still created only to be destroyed in the next step.  This is
> unfortunate, because Guix could use a different mechanism to “check out”
> files from the store to a new location.

Here’s another idea: allowing ‘guix copy’ to talk to a “raw” remote
store—i.e., just /gnu/store + /var/guix/db accessed over SSH.

Just like we have (guix store ssh), we could implement raw store
operations over SSH using ‘remote-eval’ and (guix store database).  Hmm
that amounts to implementing a subset of the daemon.

Ludo’.


  reply	other threads:[~2020-12-14  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06  9:53 guix pack file enumerator? Ricardo Wurmus
2020-12-06 19:33 ` Ryan Prior
2020-12-07 15:14 ` zimoun
2020-12-08 11:13 ` Ludovic Courtès
2020-12-09 11:04   ` Ricardo Wurmus
2020-12-14  9:48     ` Ludovic Courtès [this message]
2020-12-15  2:43       ` Ryan Prior
2020-12-15  9:53         ` Nicolò Balzarotti

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=87zh2gvhu5.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).