unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: guix pull avoidance
Date: Mon, 22 Aug 2016 14:01:17 -0400	[thread overview]
Message-ID: <20160822180117.GA17367@jasmine> (raw)
In-Reply-To: <CAEwRq=otW=2WRhD=cxYoquZ-67yQNURPS4ry8ize85E2mz7NGQ@mail.gmail.com>

On Mon, Aug 22, 2016 at 04:34:41PM +0200, Vincent Legoll wrote:
> Hello,
> 
> when one does guix pull, it is done only for that user, another one
> doing it subsequently (or at the same time) is going to download
> and compile the whole (identical) thing again, is it possible to switch
> a user to a previously dl'ed revision, like just changing a symlink in
> ~/.guix-profile to point to /gnu/store/*-guix-latest, or something like
> that ?

The 2nd user who does `guix pull` will not recompile if nothing has
changed.

You can change which Guix you use by changing what the symlink at
'~/.config/guix/latest' points to.

The next time you do `guix pull`, this symlink will be rewritten to
point at the result of the `guix pull`. That is, it will point to the
Guix built from the latest HEAD of our master branch.

> I have seen suggestions about using git as a backend for guix pull,
> but until that happen is there an easy way to get the same thing done ?

A lot of us keep a copy of Guix's Git repository, and we use the Guix we
build from that when we need something besides the latest HEAD of the
master branch.

See manual sections 8.1 Building from Git and 8.2 Running Guix Before It
Is Installed for information on how to use Guix from a Git checkout.

Some of us go even farther, and make '~/.config/guix/latest' point to
the Guix we build from Git.

  reply	other threads:[~2016-08-22 18:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22 14:34 guix pull avoidance Vincent Legoll
2016-08-22 18:01 ` Leo Famulari [this message]
2016-08-23  8:39   ` Vincent Legoll
2016-08-23 13:13     ` Vincent Legoll
2016-08-24  8:57       ` Vincent Legoll
2016-08-28 13:54         ` Vincent Legoll
2016-08-29 16:10         ` 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=20160822180117.GA17367@jasmine \
    --to=leo@famulari.name \
    --cc=help-guix@gnu.org \
    --cc=vincent.legoll@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).