From: zimoun <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>
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, 04 Dec 2020 22:30:11 +0100 [thread overview]
Message-ID: <86r1o5b6os.fsf@gmail.com> (raw)
In-Reply-To: <X8qm4BwcCh+q0sn6@jasmine.lan>
Hi,
On Fri, 04 Dec 2020 at 16:15, Leo Famulari <leo@famulari.name> wrote:
> 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.
My .bash_profile contains:
--8<---------------cut here---------------start------------->8---
export GUIX_MYPROFILES=~/.config/guix/profiles
for p in $(ls --color=no -1 $GUIX_MYPROFILES)
do
profile=${GUIX_MYPROFILES}/${p}/${p}
if [ -d $profile ]
then
GUIX_PROFILE=$profile
. $profile/etc/profile
# unset $profile
fi
done
GUIX_PROFILE=$HOME/.guix-profile
. $GUIX_PROFILE/etc/profile
# the latest Guix version lives there
# needs to be first in the PATH
GUIX_PROFILE=$HOME/.config/guix/current
. $GUIX_PROFILE/etc/profile
# Ugly workaround
export PATH="$HOME/.config/guix/current/bin${PATH:+:}$PATH"
# ~/.config/current/bin/guix repl works with readline
export GUILE_LOAD_PATH="$HOME/.guix-profile/share/guile/site/3.0${GUILE_LOAD_PATH:+:}$GUILE_LOAD_PATH"
# lastest info manual
export INFOPATH="$HOME/.config/guix/current/share/info${INFOPATH:+:}$INFOPATH"
--8<---------------cut here---------------end--------------->8---
Hope that helps.
>> Did you run “guix pull” as regular user?
>
> No, as the root user. It's the only user on that server.
So, the message seems consistent, isn’t it? I am not sure better could
be done for the root user. Well, I do not know. :-)
All the best,
simon
next prev parent reply other threads:[~2020-12-04 21:44 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
2020-12-04 21:30 ` zimoun [this message]
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
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=86r1o5b6os.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=45039@debbugs.gnu.org \
--cc=holger.peters@posteo.de \
--cc=leo@famulari.name \
--cc=ludo@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).