unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Leo Famulari <leo@famulari.name>,
	Holger Peters <holger.peters@posteo.de>
Cc: 45039@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#45039] [PATCH] Remove duplicate path declaration
Date: Fri, 04 Dec 2020 21:46:01 +0100	[thread overview]
Message-ID: <86tut1b8qe.fsf@gmail.com> (raw)
In-Reply-To: <X8qKYcAvMM7Hyjvb@jasmine.lan>

Hi Leo,

On Fri, 04 Dec 2020 at 14:13, Leo Famulari <leo@famulari.name> wrote:
> On Fri, Dec 04, 2020 at 10:51:37AM +0100, Holger Peters wrote:
>> * doc/guix.texi: Fixup path declaration.
>
>>  @example
>> -GUIX_PROFILE="$HOME/.config/guix/current/etc/profile"
>> +GUIX_PROFILE="$HOME/.config/guix/current"
>>  . "$GUIX_PROFILE/etc/profile"
>>  @end example
>
> Thanks! That example is definitely not right...
>
> However, it doesn't seem right to me either that GUIX_PROFILE should
> point to '~/.config/guix/current/etc/profile'. That profile won't
> contain anything useful related to packages the user installs. Compare
> it to the contents of '~/.guix-profile/etc/profile' to see what I mean.

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 alo was curious about the preceding paragraph, which states "Unless
> you’re on Guix System, the first time you run guix pull, be sure to
> follow the hint that the command prints [...]". I re-installed Guix on a
> Debian system and it prints this instead:
>
> ------
> hint: Consider setting the necessary environment variables by running:
>
>      GUIX_PROFILE="/root/.guix-profile"
>      . "$GUIX_PROFILE/etc/profile"
>
> Alternately, see `guix package --search-paths -p "/root/.guix-profile"'.
> ------

Did you run “guix pull” as regular user?


All the best,
simon




  reply	other threads:[~2020-12-04 21:08 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 [this message]
2020-12-04 21:15       ` Leo Famulari
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

  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=86tut1b8qe.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).