From: Leo Famulari <leo@famulari.name>
To: Nils Gillmann <niasterisk@grrlz.net>
Cc: GUIX help <help-guix@gnu.org>
Subject: Re: How can I test better?
Date: Wed, 10 Feb 2016 00:35:24 -0500 [thread overview]
Message-ID: <20160210053524.GB18281@jasmine> (raw)
In-Reply-To: <87si11gzek.fsf@grrlz.net>
On Wed, Feb 10, 2016 at 01:52:19AM +0100, Nils Gillmann wrote:
> Regarding:
> https://lists.gnu.org/archive/html/guix-devel/2016-02/msg00313.html
>
> I wonder how I can be sure if `guix environment` does not give me
> a 100% reproduction of what is happening with the files later on,
> how can I verify what I push as patch does work and which doesn't
> if I have to write the install procedure of `make` myself?
> Is `guix system vm` better?
> How can I test things *better* to give me expected results?
`guix environment` launches a new shell. It's possible to get unexpected
problems if you set environment variables in .bashrc, which is sourced
when launching interactive shells, rather than .bash_profile, which is
only sourced for login shells. This is why it's generally recommended to
set environment variables only when launching login shells.
I'm not sure what happened with lispf4 but that is one way that `guix
environment` can be broken.
You might also try the --pure and --container options to `guix
environment`, since they achieve greater degrees of isolation from the
rest of your system.
prev parent reply other threads:[~2016-02-10 5:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 0:52 How can I test better? Nils Gillmann
2016-02-10 5:35 ` Leo Famulari [this message]
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=20160210053524.GB18281@jasmine \
--to=leo@famulari.name \
--cc=help-guix@gnu.org \
--cc=niasterisk@grrlz.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.
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).