From: Ricardo Wurmus <rekado@elephly.net>
To: Hebi Li <lihebi.com@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: How to properly use channels? (my 'guix pull' throws error)
Date: Tue, 02 Oct 2018 22:19:26 +0200 [thread overview]
Message-ID: <87murwt835.fsf@elephly.net> (raw)
In-Reply-To: <87bm8c5ct8.fsf@gmail.com>
Hi,
>> Could you please tell us which “guix” you are using? “guix pull”
>> installs a new Guix to ~/.config/guix/current/bin. Are you using Guix
>> from that directory?
>
> Now I see the problem. I'm using ~/.guix-profile/bin/guix. Using
> ~/.config/guix/current/bin/guix, I'm able to build the chromium
> package.
>
> So does this mean that, I should put this path
> (~/.config/guix/current/bin) before (~/.guix-profile/bin) in $PATH?
> Otherwise it will appear that "guix pull" does not upgrade "guix".
Yes, this is correct. “guix pull” does print a message suggesting this
(at least the first time), but it is easily overlooked.
> What is the purpose of ~/.guix-profile/bin/guix then? Since it is
> symbolic linked to /gnu/store/xxx-guix, it is only updated after "guix
> package -u"?
This is how the binary installation method works; it provides a
pre-populated profile containing a fully working Guix. This was a good
idea at a time when “guix pull” would only install some Guile modules
that the system-wide “guix” command would find and load, but it can be a
bit confusing now that the “guix pull” has changed.
Maybe the binary install method needs changing. A discussion about this
has been started elsewhere on guix-devel, but it hasn’t been concluded
yet.
--
Ricardo
prev parent reply other threads:[~2018-10-02 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 2:31 How to properly use channels? (my 'guix pull' throws error) Hebi Li
2018-10-02 10:07 ` Ludovic Courtès
2018-10-02 18:10 ` Hebi Li
2018-10-02 18:22 ` Ricardo Wurmus
2018-10-02 19:16 ` Hebi Li
2018-10-02 19:42 ` Ricardo Wurmus
2018-10-02 20:11 ` Hebi Li
2018-10-02 20:19 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87murwt835.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=help-guix@gnu.org \
--cc=lihebi.com@gmail.com \
/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.