From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Eliminate environment variable hints?
Date: Tue, 19 Feb 2019 10:17:26 +0100 [thread overview]
Message-ID: <20190219091726.gp6v63jd3kqw3v6z@thebird.nl> (raw)
In-Reply-To: <20190218221809.GA12263@jurong>
On Mon, Feb 18, 2019 at 11:18:09PM +0100, Andreas Enge wrote:
> So the two are clearly not equivalent. Which of them is actually
> preferable? I find it a bit confusing that after running
> "guix package -i hello" I cannot run "hello" immediately, unlike in
> Debian.
Just running '. $PROFILE/etc/profile' is a bit dangerous. Especially on
HPC machines.
I guix-notes I also suggest to clear the other environment settings
first with
env -i /bin/bash --login --noprofile --norc
But nobody loves me for that.
We have pure 'guix environment'. Maybe we should have a 'guix run' too
which starts a new shell with only those setting applicable to the
profile. I think you can do this with 'guix environment' but it is not
too clear.
> I would not be too worried about bash vs. other shells: The current
> suggestions already would not work in csh...
it would be good to document though.
Pj.
next prev parent reply other threads:[~2019-02-19 9:24 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
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 [this message]
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=20190219091726.gp6v63jd3kqw3v6z@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=andreas@enge.fr \
--cc=guix-devel@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 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.