From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: Questions about "guix pull"
Date: Wed, 24 Feb 2016 22:17:45 +0100
Message-ID: <87egc1erk6.fsf@gnu.org>
References: <8760xnra9y.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:55779)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1aYgoj-0003LO-IR
	for help-guix@gnu.org; Wed, 24 Feb 2016 16:17:54 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1aYgoe-0000JO-JW
	for help-guix@gnu.org; Wed, 24 Feb 2016 16:17:53 -0500
In-Reply-To: <8760xnra9y.fsf@gmail.com> (Chris Marusich's message of "Wed, 17
	Feb 2016 00:50:01 -0800")
List-Id: <help-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/help-guix>
List-Post: <mailto:help-guix@gnu.org>
List-Help: <mailto:help-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-guix>,
	<mailto:help-guix-request@gnu.org?subject=subscribe>
Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org
Sender: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org

Chris Marusich <cmmarusich@gmail.com> skribis:

> I have read the Info node "(guix) Invoking guix pull", but it doesn't
> seem to answer the following questions:
>
> - Who is allowed to run "guix pull"? Only root? Any user?
>
> - After a successful "guix pull", are the new guix tools and package
>   definitions visible to everyone, regardless of who ran the command?

I=E2=80=99ve added a paragraph to clarify that:

  Any user can update their Guix copy using @command{guix pull}, and the
  effect is limited to the user who run @command{guix pull}.  For
  instance, when user @code{root} runs @command{guix pull}, this has no
  effect on the version of Guix that user @code{alice} sees, and vice
  versa@footnote{Under the hood, @command{guix pull} updates the
  @file{~/.config/guix/latest} symbolic link to point to the latest Guix,
  and the @command{guix} command loads code from there.}.

> - Are there any best practices, or pitfalls to avoid, when using "guix
>   pull"?

Currently =E2=80=98guix pull=E2=80=99 updates only the Scheme part of Guix,=
 which is
certainly the most important thing but not the only thing: see
<http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D22629>.

> - I understand that some people don't use "guix pull" and instead just
>   run guix from a local git checkout. Should the manual also explain why
>   you might want to do that and how it can be done?

I think this is mostly due to the fact that (1) many users are also Guix
developers, so they have a Git checkout around anyway ;-), (2) using the
Git checkout is usually faster (currently =E2=80=98guix pull=E2=80=99 redow=
nloads the
whole thing.)

There=E2=80=99s also the problem that =E2=80=98guix pull=E2=80=99 does not =
authenticate the code
it downloads; the problem is also present with Git, though (currently
only release tags are signed in Guix.)  All this needs to be fixed!

> I'm happy to submit a patch to improve this Info node, but I need to
> understand "guix pull" first.

Sure!

Thanks for your feedback,
Ludo=E2=80=99.