From: Fis Trivial <ybbs.daans@hotmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Export environment variables only in `guix environment`.
Date: Thu, 1 Feb 2018 15:15:40 +0000 [thread overview]
Message-ID: <MWHPR16MB006310ED9D06D1464570001B92FA0@MWHPR16MB0063.namprd16.prod.outlook.com> (raw)
In-Reply-To: <20180201052211.GA21222@thebird.nl>
Pjotr Prins writes:
> On Thu, Feb 01, 2018 at 12:40:39AM +0100, Ludovic Courtès wrote:
>> Hello,
>>
>> Fis Trivial <ybbs.daans@hotmail.com> skribis:
>>
>> > * Problem
>> > The exported environment variables can cause various problems in foreign
>> > distribution(1)(2). And besides, The long list of environment variables(4)
>> > injected into user's login shell makes the user's environment impure.
>> > So, I believe that if I want to run guix safely on a foreign distributions, I
>> > need to eliminate the need for exporting environment variables from guix to my
>> > login shell.
>
> Not a problem, just don't do it :). To import the invironments
> run
>
> . $PROFILE/etc/profile
>
> I do that in scripts or when I need something. Even so, many programs
> work with just the PATH set.
>
> Pj.
Currently my solution is separating the profile file into two parts, one
contains PATH and SSL related envs, the second part contains all the
others exported by guix. Then I source the first part in login shell
while the second part in interactive shell.
It's a little hack, which means not the way it should work, to me that's
a problem. Guix is still young, we don't have many legacy problems that
needs hacks to solve. I love guix project, which is elegant from the
choice of scripting language and the underlying functional logic. I hope
that if we be picky enough, Guix can stay this way. So lets eliminate
these hacks. :)
Thanks for your time.
next prev parent reply other threads:[~2018-02-01 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 22:29 Export environment variables only in `guix environment` Fis Trivial
2018-01-31 23:40 ` Ludovic Courtès
2018-02-01 5:22 ` Pjotr Prins
2018-02-01 15:15 ` Fis Trivial [this message]
2018-02-01 15:06 ` Fis Trivial
2018-02-01 17:26 ` Chris Marusich
2018-02-02 6:27 ` Pjotr Prins
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=MWHPR16MB006310ED9D06D1464570001B92FA0@MWHPR16MB0063.namprd16.prod.outlook.com \
--to=ybbs.daans@hotmail.com \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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).