From: Brett Gilio <brettg@posteo.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Eliminate environment variable hints?
Date: Mon, 18 Feb 2019 16:02:43 -0600 [thread overview]
Message-ID: <87k1hw92m4.fsf@posteo.net> (raw)
In-Reply-To: <87a7iswyki.fsf@elephly.net>
Ricardo Wurmus writes:
> Hi Guix,
>
> when installing a package into a profile Guix very helpfully tells you
> that you may need to set certain environment variables. It doesn’t tell
> you that these environment variables can also be set by source’ing the
> generated etc/profile file.
>
> I have seen the bashrc and bash_profile files of many users and they are
> usually full of conflicting environment variable definitions. In these
> files I often also see these Guix recommendations.
>
> I think Guix should suggest sourcing the generated etc/profile file
> instead of listing explicit environment variable definitions. It would
> be less noisy and less confusing, in my opinion.
>
> What do you think?
>
> (What about people who don’t use Bash?)
I think this is a good idea. It may also be worth mentioning that these
suggestions can also be set in environments using the --search-paths
flag. I know that is said in the documentation, but maybe it could be
highlighted somehow?
Brett Gilio
next prev parent reply other threads:[~2019-02-18 22:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 21:56 Eliminate environment variable hints? Ricardo Wurmus
2019-02-18 22:02 ` Brett Gilio [this message]
2019-02-18 22:08 ` Pierre Neidhardt
2019-02-18 22:18 ` Andreas Enge
2019-02-19 7:41 ` Ricardo Wurmus
2019-02-19 8:10 ` Andreas Enge
2019-02-22 4:44 ` Chris Marusich
2019-02-19 9:17 ` Pjotr Prins
2019-02-19 9:34 ` Ricardo Wurmus
2019-02-19 10:14 ` Pjotr Prins
2019-03-04 21:56 ` Ludovic Courtès
2019-03-06 13:25 ` Ricardo Wurmus
2019-03-06 13:48 ` Dan Frumin
2019-03-18 4:52 ` Chris Marusich
2019-04-11 8:45 ` Ludovic Courtès
2019-04-12 15:10 ` Chris Marusich
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=87k1hw92m4.fsf@posteo.net \
--to=brettg@posteo.net \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.