From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35942@debbugs.gnu.org
Subject: bug#35942: guix install: environment variable message is very confusing
Date: Thu, 30 May 2019 09:07:30 +0200 [thread overview]
Message-ID: <871s0gl8st.fsf@elephly.net> (raw)
In-Reply-To: <87sgsyvc0e.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> Tobias Geerinckx-Rice <me@tobias.gr> skribis:
>
>> Robert Vollmert wrote:
>>> Suggestion to instead print:
>>>
>>> Set the following environment variables to use <package> right away:
>>
>> Thanks for the bug report! Related (not duplicate) thread:
>>
>> <https://lists.gnu.org/archive/html/guix-devel/2019-02/msg00362.html>
>
> I don’t think we reached a conclusion back then. I’m fine with Robert’s
> suggestion, but do people think it will really help?
>
> Others were in favor of dropping this message altogether, which I think
> wouldn’t be a good idea: how would people discover about search path
> handling?
I was in favour of *replacing* the message with the suggestion to run
export GUIX_PROFILE=/this/profile
source $GUIX_PROFILE/etc/profile
because it usually does the right thing.
It looks less overwhelming than the individual list of environment
variables. I’ve seen a lot of people who added all of these variables
to their bashrc (or bash_profile if they talked to me before), which is
not what we want to encourage.
We can also hint at “guix package --search-paths” to see a full list of
environment variables for people who want to set them manually right
here and now.
--
Ricardo
next prev parent reply other threads:[~2019-05-30 7:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 11:17 bug#35942: guix install: environment variable message is very confusing Robert Vollmert
2019-05-28 12:08 ` Tobias Geerinckx-Rice
2019-05-28 15:23 ` Ludovic Courtès
2019-05-30 7:07 ` Ricardo Wurmus [this message]
2019-05-31 16:45 ` Andreas Enge
2019-05-31 21:19 ` Ludovic Courtès
2019-06-06 7:48 ` Ludovic Courtès
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=871s0gl8st.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35942@debbugs.gnu.org \
--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).