unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Questions about "guix pull"
Date: Wed, 17 Feb 2016 12:05:03 +0200	[thread overview]
Message-ID: <20160217120503.1831f727@debian-netbook> (raw)
In-Reply-To: <8760xnra9y.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]

On Wed, 17 Feb 2016 00:50:01 -0800
Chris Marusich <cmmarusich@gmail.com> wrote:

> Hi,
> 
> 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?

Anybody can. Also, each user (and root) have their own snapshot of the guix
packages, so knowing that someone else just ran `guix pull` won't allow you
to upgrade your packages. One way it will help you, is if there's been no
change to git between the last pull on the system (by anybody) and the next
pull, the next one will reuse the definitions already saved on the machine
and not recompile them.

> - After a successful "guix pull", are the new guix tools and package
>   definitions visible to everyone, regardless of who ran the command?
 
Available to whomever ran the command.

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

In "guix on a foreign distro (aka not GuixSD)" /usr/bin/local/guix is a
symlink to root's copy of guix. When I notice that the guix binary has been
updated, I also run `sudo guix pull && sudo guix package -u`. As above, `guix
pull && sudo guix pull` will likely get the speed benefit for the sudo guix
pull.
 
> - 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?

The manual does have a section about using guix before installing. 8.1 and
8.2 has some information about that.

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

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-02-17 10:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17  8:50 Questions about "guix pull" Chris Marusich
2016-02-17 10:05 ` Efraim Flashner [this message]
2016-02-17 18:26   ` Andreas Enge
2016-02-24 21:17 ` Ludovic Courtès
2016-02-24 21:25   ` Andreas Enge
2016-02-27 17:25     ` Ludovic Courtès
2016-02-27 19:10       ` Leo Famulari
2016-03-03  3:18         ` Chris Marusich

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=20160217120503.1831f727@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=cmmarusich@gmail.com \
    --cc=help-guix@gnu.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.
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).