From: HiPhish <hiphish@posteo.de>
To: help-guix@gnu.org
Subject: Re: I don't understand profiles and directories
Date: Sat, 19 Jan 2019 18:55:33 +0100 [thread overview]
Message-ID: <5645159.Nm1EbChBH9@aleksandar-ixtreme-m5740> (raw)
In-Reply-To: <8736pofuio.fsf@elephly.net>
On Saturday, 19 January 2019 18:05:03 CET you wrote:
> I don’t think so. It should print a file name.
The message must have cut off, there was a full file path into `/gnu/
store/...`.
> > Should I change my `.profile` file to be like this instead?
> >
> > source "$HOME/.guix-profile/etc/profile"
> > export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale"
> > export PATH="$HOME/.config/guix/current/bin:$PATH"
> > export INFOPATH="$HOME/.config/guix/current/share/info:$INFOPATH"
> >
> > I.e. first source the Guix profile, which will add itself to the `$PATH`,
> > and then add the path to the other profile.
>
> Yes.
OK, now it seems to work. Just to re-iterate, the Guix binary I'm going to
invoke from the command line (`guix`) comes from this profile `~/.config/guix/
current/`, while all my packages are in the `~/.guix-profile` profile, correct?
This means that the Guix binary from `~/.config/guix/current/` shadows the one
from `~/.guix-profile`.
My complete `~/.profile` file now contains
source "$HOME/.guix-profile/etc/profile"
export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale"
export PATH="$HOME/.config/guix/current/bin:$PATH"
export INFOPATH="$HOME/.config/guix/current/share/info:$INFOPATH"
# SSL certificates (after installing 'nss-certs')
export SSL_CERT_DIR="$HOME/.guix-profile/etc/ssl/certs"
export SSL_CERT_FILE="$HOME/.guix-profile/etc/ssl/certs/ca-certificates.crt"
export GIT_SSL_CAINFO="$SSL_CERT_FILE"
and `which guix` prints
/home/username/.config/guix/current/bin/guix
next prev parent reply other threads:[~2019-01-19 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 16:13 I don't understand profiles and directories HiPhish
2019-01-19 16:27 ` Ricardo Wurmus
2019-01-19 16:54 ` HiPhish
2019-01-19 17:05 ` Ricardo Wurmus
2019-01-19 17:55 ` HiPhish [this message]
2019-01-19 21:00 ` Ricardo Wurmus
2019-01-19 23:20 ` HiPhish
2019-01-19 23:31 ` Ricardo Wurmus
2019-01-19 23:34 ` HiPhish
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=5645159.Nm1EbChBH9@aleksandar-ixtreme-m5740 \
--to=hiphish@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).