unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: HiPhish <hiphish@posteo.de>
To: help-guix@gnu.org
Subject: Re: I don't understand profiles and directories
Date: Sun, 20 Jan 2019 00:20:54 +0100	[thread overview]
Message-ID: <1600005.yDqdFR1sp3@aleksandar-ixtreme-m5740> (raw)
In-Reply-To: <87zhrwe54v.fsf@elephly.net>

On Saturday, 19 January 2019 22:00:20 CET you wrote:
> > 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.
Here is what I have:

    $ cd ~/.guix-profile/bin
    $ ls | grep guix
    guix
    guix-daemon

    $ file guix guix-daemon 
    guix: symbolic link to /gnu/store/vv1kkj9aqpv1akk7l7vp2kkd695wgxcr 
guix-0.16.0-8.7ba2b27/bin/guix
    guix-daemon: symbolic link to /gnu/store/vv1kkj9aqpv1akk7l7vp2kkd695wgxcr-
guix-0.16.0-8.7ba2b27/bin/guix-daemon

    $ ./guix --version
    guix (GNU Guix) 0.16.0-8.7ba2b27

    $ guix --version
    guix (GNU Guix) 8d09e97b8cdde9dcceb2353112613a3fee63426d

So both are symlinks to items in the store, and they are distinct from the 
Guix that's in my $PATH.

> > 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).
OK, got it.

  reply	other threads:[~2019-01-19 23:21 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
2019-01-19 23:20           ` HiPhish [this message]
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=1600005.yDqdFR1sp3@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).