From: Ricardo Wurmus <rekado@elephly.net>
To: HiPhish <hiphish@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: I don't understand profiles and directories
Date: Sat, 19 Jan 2019 22:00:20 +0100 [thread overview]
Message-ID: <87zhrwe54v.fsf@elephly.net> (raw)
In-Reply-To: <5645159.Nm1EbChBH9@aleksandar-ixtreme-m5740>
HiPhish <hiphish@posteo.de> writes:
> 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/...`.
That’s not correct. This indicates that the GUIX_PROFILE variable is
not exported.
> 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?
Yes.
> This means that the Guix binary from `~/.config/guix/current/` shadows the one
> from `~/.guix-profile`.
There shouldn’t be any “guix” package in ~/.guix-profile.
>
> My complete `~/.profile` file now contains
>
> source "$HOME/.guix-profile/etc/profile"
I’d replace this with:
export GUIX_PROFILE=$HOME/.guix-profile
source $GUIX_PROFILE/etc/profile
This ensures that the variables won’t point to specific store items but
rather to the *current* generation (even when you upgrade).
> and `which guix` prints
>
> /home/username/.config/guix/current/bin/guix
Good!
--
Ricardo
next prev parent reply other threads:[~2019-01-20 12:47 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
2019-01-19 21:00 ` Ricardo Wurmus [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhrwe54v.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=hiphish@posteo.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.