all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Marco van Zwetselaar <zwets@zwets.com>
Cc: guix-devel@gnu.org
Subject: Re: Malconnected machines & guix pull
Date: Thu, 10 Mar 2016 16:44:30 +0100	[thread overview]
Message-ID: <idjh9gewd5t.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <56E15AF6.5040806@zwets.com>


Marco van Zwetselaar <zwets@zwets.com> writes:

> In fact, what I am really looking for is a --substitute-urls option for 
> 'guix pull', or a way to separate the pull and the subsequent build, so 
> that I can make it connect to a 'guix publish'-ing server.

Instead of “guix pull” may I suggest using git instead?  Especially,
when you have multiple machines on which Guix should run, it may make
sense to just clone the Guix git repository once from the Internet,
clone it to the other machines via local network, and then update once
in a while via “git pull” (not “guix pull”).

You can create a link “~/.config/guix/latest” pointing to, say,
“~/dev/guix” (if that’s the directory holding the cloned repository).

When you update with “git pull” you’ll only have to download recent
changes, not the whole Guix code.

Does this make sense?

~~ Ricardo

  reply	other threads:[~2016-03-10 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 11:31 Malconnected machines & guix pull Marco van Zwetselaar
2016-03-10 15:44 ` Ricardo Wurmus [this message]
2016-03-10 17:04   ` Pjotr Prins
2016-03-11 13:39     ` Ricardo Wurmus
2016-03-10 17:53   ` [PATCH] doc: Add footnote about pointing ~/.config/guix/latest at user's checkout Christopher Allan Webber
2016-03-11 13:41     ` Ricardo Wurmus
2016-03-11 16:42       ` Christopher Allan Webber
2016-03-11 14:40     ` Ludovic Courtès
2016-03-23  8:52   ` Malconnected machines & guix pull Marco van Zwetselaar
2016-03-23 11:06     ` Ricardo Wurmus

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=idjh9gewd5t.fsf@bimsb-sys02.mdc-berlin.net \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=guix-devel@gnu.org \
    --cc=zwets@zwets.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.