unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: myglc2 <myglc2@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: "The following environment variable definitions may be needed"
Date: Wed, 10 May 2017 09:39:49 -0400	[thread overview]
Message-ID: <86ziekygnu.fsf@gmail.com> (raw)
In-Reply-To: <87shkcvs33.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 10 May 2017 14:01:20 +0200")

On 05/10/2017 at 14:01 Ludovic Courtès writes:

> Hi!
>
> Chris Marusich <cmmarusich@gmail.com> skribis:
>
>> This leads to my question: If I'm using GuixSD (or a foreign distro in
>> which $GUIX_PROFILE/etc/profile is automatically sourced), do I need to
>> add these recommended export statements to my ~/.bashrc or
>> ~/.bash_profile?
>
> No.
>
>> My suspicion is that the answer is "no".  The next time I reboot or log
>> out and back in, the environment variables will be set correctly even if
>> I don't add them to my ~/.bashrc or ~/.bash_profile.  In fact, by adding
>> them there, I would be adding redundant entries.  I am hoping that
>> someone can confirm that my understanding is correct.
>
> Confirmed!
>
> I think the recommendations that ‘guix package’ produces are still
> useful though, precisely because $GUIX_PROFILE/etc/profile won’t be
> re-sourced until you log in again.

These messages were a source of confusion for me.  It is really great to
see this clarified.

What if we change the message from ...

The following environment variable definitions may be needed:
   export PATH="test-profile/bin${PATH:+:}$PATH"

... to ...

If you need the package before the next login, do:
   export PATH="test-profile/bin${PATH:+:}$PATH"

> Exercise for the reader: extend Bash with Guile-Bash such that the new
> environment variable settings are automatically effected when ‘guix
> package’ is run.  :-)

This sounds cool. Could you please expand on it a bit?

  reply	other threads:[~2017-05-10 13:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10  5:53 "The following environment variable definitions may be needed" Chris Marusich
2017-05-10  9:19 ` ng0
2017-05-10 12:01 ` Ludovic Courtès
2017-05-10 13:39   ` myglc2 [this message]
2017-05-10 21:49     ` Niall Dooley
2017-05-11  8:55       ` Ludovic Courtès
2017-05-11 19:55         ` Niall Dooley

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=86ziekygnu.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=help-guix@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.
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).