From: Ricardo Wurmus <rekado@elephly.net>
To: Gottfried <gottfried@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: guix pull
Date: Wed, 16 Feb 2022 23:58:37 +0100 [thread overview]
Message-ID: <87czjm4dhv.fsf@elephly.net> (raw)
In-Reply-To: <9297ba25-48d0-f8e4-ff8e-f16dda50c597@posteo.de>
Gottfried <gottfried@posteo.de> writes:
> 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"...
Your shell (by default that’s GNU Bash) has a few builtin commands, but
when you type something like “ls” or “guix” it has to search for an
executable of that name on your disk.
It searches the directories that are listed on the PATH environment
variable. You can see the value of PATH by running
echo $PATH
This will be a colon-separated list of directories that can be expected
to contain executables. When you type “guix” and hit enter your shell
visits the directories listed in this PATH variable one by one until it
finds an executable with the name “guix”. It then remembers the
location so that it doesn’t have to do all that work again.
The hint above tells you to put ~/.config/guix/current/bin *first* on
the list of directories in the PATH variable, so that when the shell
goes to search for “guix” it will look there first and find
~/.config/guix/current/bin/guix — and not /usr/local/bin/guix or
whatever else might exist on your disk.
Since bash might have already remembered that “guix” corresponds to
“/usr/local/bin/guix” you need to tell it to forget about that and look
again. That’s what “hash guix” does.
You can set PATH permanently by adding or modifying a line in the
~/.bash_profile file, which is read once when Bash starts. Or you can
set it just in the current shell session.
In any case, setting this variable is done like this:
export PATH=/home/gottfried/.config/guix/current/bin:$PATH
This changes the value of PATH so that
“/home/gottfried/.config/guix/current/bin” appears first, followed by
the current value of PATH. You can add this line to the bottom of
~/.bash_profile and then start a new shell session (e.g. by logging out
and in again).
--
Ricardo
prev parent reply other threads:[~2022-02-16 23:07 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
2022-02-16 22:58 ` Ricardo Wurmus [this message]
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=87czjm4dhv.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gottfried@posteo.de \
--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).