From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: guix 0.7 installation Date: Sun, 14 Sep 2014 16:24:57 +0200 Message-ID: <87iokqb7pi.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44110) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XTAjh-0004Bh-4u for guix-devel@gnu.org; Sun, 14 Sep 2014 10:25:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XTAjb-0002gb-7a for guix-devel@gnu.org; Sun, 14 Sep 2014 10:25:05 -0400 Received: from hera.aquilenet.fr ([2a01:474::1]:42178) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XTAja-0002gI-PK for guix-devel@gnu.org; Sun, 14 Sep 2014 10:24:59 -0400 In-Reply-To: (Federico Beffa's message of "Sat, 13 Sep 2014 14:08:33 +0200") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Federico Beffa Cc: guix-devel@gnu.org Federico Beffa skribis: > Having played with guix a little bit, I have a few questions: > > - My locally built guix is now built with references to guix libraries > (in /gnu/store). What happens if I "guix pull" and "guix package -u" > and then garbage collect old profiles and packages? Is it possible > that at some point my guix will break? It=E2=80=99s possible. However, since all the tools needed to build Guix a= re now in your profile, you=E2=80=99ll always be able to do =E2=80=98make clea= n && make && make install=E2=80=99. > - Every time I use guix I get the following note: > > ;;; note: source file /usr/local/share/guile/site/2.0/srfi/srfi-37.scm > ;;; newer than compiled /usr/local/share/guile/site/2.0/srfi/srfi= -37.go > > I guess it is just a matter of recompiling the module, but the > "make install" procedure should in principle get it right. Indeed. Having checked the makefile, I don=E2=80=99t see why it doesn=E2= =80=99t happen, since =E2=80=98make install=E2=80=99 does do the right thing for all the ot= her .go files. However, I wouldn=E2=80=99t worry too much, since this file is no longer ne= eded if you use a recent Guile. > - Out of curiosity I've installed the guix package into my store. The > installation procedure suggested to define the following environment > variables: > > export GUILE_LOAD_PATH=3D"$HOME/.guix-profile/share/guile/site/2.0" > export GUILE_LOAD_COMPILED_PATH=3D"$HOME/.guix-profile/share/guile/site= /2.0" > > I did that. However, the guix package binary was still pointing to > my local copy of object files in "/usr/local/share/guile/...". That > sounded a little worrying to me. For this reason, for the moment, I > just removed the guix package. Is there a way to force the guix > package binary to only look in the store for object files? If you look at the =E2=80=98guix=E2=80=99 program, you=E2=80=99ll see that = it adds its own module directory at the front of the search path. Thus, /usr/local/bin/guix will always look at things in /usr/local/share/guile first. Conversely, /gnu/.../bin/guix will always look at /gnu/.../share/guile first. This is on purpose, to make sure we don=E2=80=99t inadvertently mix different versions. (Actually the very first thing in the search path is ~/.config/guix/latest, which is populated by =E2=80=98guix pull=E2=80=99.) > - If I would install the guix package and uninstall the locally built > one from /usr/local, how would a new user be able to start using > guix? They could get started by using, say, ~federico/.guix-profile/bin/guix to install Guix in their own profile. > - To use the build tools from the stores I've defined the following > environment variables: > > export PKG_CONFIG_PATH=3D"$HOME/.guix-profile/lib/pkgconfig" > export ACLOCAL_PATH=3D"$HOME/.guix-profile/share/aclocal" > export CPATH=3D"$HOME/.guix-profile/include" > export LIBRARY_PATH=3D"$HOME/.guix-profile/lib" > > Is it possible that having these variables defined does interfere > with the workings of my host distribution (Debian 7.6)? What > happens, say, if an install script for a Debian package makes use of > pkg-config (or any other tool) and there is a difference between the > one expected by the Debian package (reported by ATP tools) and the > one found on my system? Should I better not have these variables > defined by default? I don=E2=80=99t think APT=E2=80=99s scripts can be influenced by these envi= ronment variables, at least as long as they=E2=80=99re not defined in a global file= such as /etc/profile. Most of us have been using Guix on top of some other distro anyway, at least until recently. Thanks, Ludo=E2=80=99.