From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: How can I test better? Date: Wed, 10 Feb 2016 00:35:24 -0500 Message-ID: <20160210053524.GB18281@jasmine> References: <87si11gzek.fsf@grrlz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41294) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTNR2-00005K-BH for help-guix@gnu.org; Wed, 10 Feb 2016 00:35:29 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aTNQy-0000ZP-7Q for help-guix@gnu.org; Wed, 10 Feb 2016 00:35:28 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:44259) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTNQy-0000ZH-3D for help-guix@gnu.org; Wed, 10 Feb 2016 00:35:24 -0500 Content-Disposition: inline In-Reply-To: <87si11gzek.fsf@grrlz.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org To: Nils Gillmann Cc: GUIX help 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.