From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57615) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cymMU-0002KJ-87 for guix-patches@gnu.org; Thu, 13 Apr 2017 17:33:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cymMQ-00044H-5w for guix-patches@gnu.org; Thu, 13 Apr 2017 17:33:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:47977) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cymMQ-000448-2A for guix-patches@gnu.org; Thu, 13 Apr 2017 17:33:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cymMP-0008TZ-SM for guix-patches@gnu.org; Thu, 13 Apr 2017 17:33:01 -0400 Subject: bug#26366: [PATCH] doc: Specify that Guix should be built from within a container. Resent-To: guix-patches@gnu.org Resent-Message-ID: References: <87inmjcn1o.fsf@lassieur.org> <20170405074943.27404-1-clement@lassieur.org> <87bms7qdhu.fsf@gnu.org> <87a87k46f3.fsf@lassieur.org> <87wpao80jp.fsf@gnu.org> From: =?UTF-8?Q?Cl=C3=A9ment?= Lassieur In-reply-to: <87wpao80jp.fsf@gnu.org> Date: Thu, 13 Apr 2017 23:32:31 +0200 Message-ID: <87fuhc9eog.fsf@lassieur.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 26366-close@debbugs.gnu.org Ludovic Courtès writes: > Hello! > > Clément Lassieur skribis: > >> Ludovic Courtès writes: >> >>> Clément Lassieur skribis: >>> >>>> * doc/contributing.texi: add '--container' and '--network' options to the >>>> 'guix environment guix' command. >>> >>> [...] >>> >>>> +course, by using Guix! The following command starts a new shell within >>>> +an isolated container where all the dependencies and appropriate >>>> +environment variables are set up to hack on Guix: >>>> >>>> @example >>>> -guix environment guix >>>> +guix environment --container --network guix >>>> @end example >>> >>> What’s the rationale? Was this to address the warnings in your first >>> message? >> >> This was both to address the warnings in my first message, and my build >> error. I apologize if my message is (still) not clear, but it is >> difficult to reproduce those bugs, since they are state-dependent. > > Yeah, I see. > >>> It’s possible and a good way to silence the warnings you were seeing, >>> but it should work fine without it too. >> >> I don't understand why it should work fine. Guix (or Guile-SSH, for >> example) both depend on Guile 2.0 (which is an input). But let's say >> that on my system, Guile 2.2 is installed instead. I want to build Guix >> (or Guile-SSH). I usually do 'guix environment guix' (or 'guix >> environment guile-ssh'). Then, in my opinion, 'guile --version' should >> output 2.0, but it outputs 2.2. Is it supposed to build with the wrong >> Guile? (If I do 'guix environment -C guix', then 'guile --version' >> outputs 2.0.) > > ‘guix environment’ definitely prepends things to PATH et al. > > Could it be that you have variable definitions in the wrong Bash init > files as noted in > ? Oh... yes that's it :) Sorry the waste of time, I should have followed the documentation. I close the bug, since I think it's all related to this. Thanks, Clément