unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Gottfried <gottfried@posteo.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: guix pull
Date: Wed, 16 Feb 2022 20:38:33 +0000	[thread overview]
Message-ID: <9297ba25-48d0-f8e4-ff8e-f16dda50c597@posteo.de> (raw)
In-Reply-To: <87leya4lmn.fsf@elephly.net>

Now I did a guix pull in root.

It asks me at the end:


Hinweis: Nachdem Sie `PATH' festgelegt haben, sollten Sie `hash guix' 
ausführen, damit Ihre Shell `/root/.config/guix/current/bin/guix' verwendet.

What does it mean?

How do I "PATH"...


Gottfried



Am 16.02.22 um 21:09 schrieb Ricardo Wurmus:
> Gottfried<gottfried@posteo.de>  writes:
>
>> Should I do a guix pull basically in my user account?
>>
>> Or should I do a guix pull basically in the root account?
>>
>> As far as I understood if I do a gux pull in my user account, it has
>> no influence to the root account?
> This is correct.  As far as Guix is concerned “root” is just another
> user account.
>
>> But If I do a guix pull only in my user account, it would mean, as far
>> as I understand it, the root account would not get security updates?
> Correct.
>
> Note that “guix pull” alone doesn’t upgrade any installed packages.  It
> only gives you a new version of Guix which has access to updated packages.
>
>> What should be the procedure?
> You can have all users on the machine share the same guix and/or the
> same profile and upgrade just that.
>
> On a single-user system it also makes sense to just not install any
> software for the root user.
>

  parent reply	other threads:[~2022-02-16 20:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 16:28 guix pull Gottfried
2022-02-16 17:19 ` Leo Famulari
2022-02-16 17:55   ` pelzflorian (Florian Pelz)
2022-02-16 19:22     ` Gottfried
2022-02-16 19:28   ` Gottfried
2022-02-16 20:27     ` Leo Famulari
2022-02-16 20:09 ` Ricardo Wurmus
2022-02-16 20:35   ` Gottfried
2022-02-16 22:36     ` Ricardo Wurmus
2022-02-16 20:38   ` Gottfried [this message]
2022-02-16 22:58     ` 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

  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=9297ba25-48d0-f8e4-ff8e-f16dda50c597@posteo.de \
    --to=gottfried@posteo.de \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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).