all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 45039@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
	"Holger Peters" <holger.peters@posteo.de>
Subject: [bug#45039] [PATCH] Remove duplicate path declaration
Date: Fri, 4 Dec 2020 16:15:12 -0500	[thread overview]
Message-ID: <X8qm4BwcCh+q0sn6@jasmine.lan> (raw)
In-Reply-To: <86tut1b8qe.fsf@gmail.com>

On Fri, Dec 04, 2020 at 09:46:01PM +0100, zimoun wrote:
> Well, from my understanding, doing this:
> 
>         GUIX_PROFILE=$HOME/.config/guix/current
>         . $GUIX_PROFILE/etc/profile
> 
> allows to have the guix commands that refer to the latest version “guix
> pull”’ed.   Moreover, you also have the last version of the manual with:
> 
> --8<---------------cut here---------------start------------->8---
> export INFOPATH="$HOME/.config/guix/current/share/info${INFOPATH:+:}$INFOPATH"
> --8<---------------cut here---------------end--------------->8---
> 
> To me, the manual is right for this part.  Maybe I am missing something.

I suppose that one could source both 'etc/profile' directories, from
~/.guix-profile and ~/.config/guix/current.

> Did you run “guix pull” as regular user?

No, as the root user. It's the only user on that server.




  reply	other threads:[~2020-12-04 21:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04  9:44 [bug#45039] Duplicate folders in docs Holger Peters
2020-12-04  9:51 ` [bug#45039] [PATCH] Remove duplicate path declaration Holger Peters
2020-12-04 19:13   ` Leo Famulari
2020-12-04 20:46     ` zimoun
2020-12-04 21:15       ` Leo Famulari [this message]
2020-12-04 21:30         ` zimoun
2020-12-07  9:04     ` Ludovic Courtès
2020-12-07 19:31       ` Leo Famulari
2021-07-16  2:09       ` bug#45039: Duplicate folders in docs Maxim Cournoyer
2020-12-04 18:59 ` [bug#45039] " zimoun
2020-12-04 19:01   ` zimoun

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=X8qm4BwcCh+q0sn6@jasmine.lan \
    --to=leo@famulari.name \
    --cc=45039@debbugs.gnu.org \
    --cc=holger.peters@posteo.de \
    --cc=ludo@gnu.org \
    --cc=zimon.toutoune@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.