unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: t_w_@freenet.de
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Root guix dereferencing
Date: Mon, 19 Nov 2018 15:07:06 +0100	[thread overview]
Message-ID: <87efbhnotx.fsf@lassieur.org> (raw)
In-Reply-To: <dcf27d64-a7cf-fb53-c855-64f810401049@freenet.de>

Thorsten Wilms <t_w_@freenet.de> writes:

> On 19/11/2018 11.20, Clément Lassieur wrote:
>
>> This is because the result of running guix pull is a profile available
>> under ~/.config/guix/current containing the latest Guix[1].
>>
>> So you may need to make sure it is at the beginning of your search path.
>
> Thanks, but the plain user `guix pull` works fine and ~/.config/guix/current
> is up-to-date.

In case it's not clear, '~' refers to root's home as well.  'root' is
just a user.  You don't even have to use it at all.  (I personally never
use it.)

>> [1]: https://www.gnu.org/software/guix/manual/en/html_node/Invoking-guix-pull.html
>
> I note that this page doesn't contain "sudo" at all and "root" only once, in
> "For instance, when user root runs guix pull, this has no effect on the
> version of Guix that user alice sees, and vice versa.".

It doesn't need to contain 'sudo' and 'root', because 'root' is just a
user, so everything works the same way.

Clément

  reply	other threads:[~2018-11-19 14:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-17 11:17 Root guix dereferencing Thorsten Wilms
2018-11-18 23:06 ` Leo Famulari
2018-11-19  9:12   ` Thorsten Wilms
2018-11-19 10:20     ` Clément Lassieur
2018-11-19 11:47       ` Thorsten Wilms
2018-11-19 14:07         ` Clément Lassieur [this message]
2018-11-19 14:32           ` Thorsten Wilms
2018-11-19 15:06             ` Clément Lassieur
2018-11-19 17:08               ` Thorsten Wilms
2018-11-19 18:27                 ` Clément Lassieur

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=87efbhnotx.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=help-guix@gnu.org \
    --cc=t_w_@freenet.de \
    /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).