From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#22629: [PATCH 0/4] 'guix pull' produces a self-contained Guix Date: Wed, 06 Jun 2018 15:27:59 +0200 Message-ID: <87d0x4jb8g.fsf@gnu.org> References: <87fu45ve2z.fsf@gnu.org> <20180531144337.16298-1-ludo@gnu.org> 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]:60886) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fQYUq-000807-H1 for bug-guix@gnu.org; Wed, 06 Jun 2018 09:29:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fQYUo-0000K1-FX for bug-guix@gnu.org; Wed, 06 Jun 2018 09:29:04 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:56359) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fQYUo-0000Jv-BN for bug-guix@gnu.org; Wed, 06 Jun 2018 09:29:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fQYUo-0003XB-3c for bug-guix@gnu.org; Wed, 06 Jun 2018 09:29:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: (Fis Trivial's message of "Tue, 5 Jun 2018 16:47:20 +0000") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Fis Trivial Cc: "22629@debbugs.gnu.org" <22629@debbugs.gnu.org> Hello! Fis Trivial skribis: >> The result of running =E2=80=98guix pull=E2=80=99 is a =E2=80=9Cpro= file=E2=80=9D available under >> =E2=80=98~/.config/guix/current=E2=80=99 containing the latest Guix. = Thus, make sure to >> add it to the beginning of your search path so that you use the latest >> version, and similarly for the Info manual (*note Documentation::): >> >> export PATH=3D"$HOME/.config/guix/current/bin:$PATH" >> export INFOPATH=3D"$HOME/.config/guix/current/share/info:$INFOPAT= H" >> > > This sounds like something could be done by guix itself, choosing the > right profile path by $HOME. Since guix has absolute control about this > piece of information? I think it would be bad for Guix to modify your ~/.bashrc directly, so it=E2=80=99s better to let users do that. GuixSD will have the right PATH and INFOPATH by default, though. >> Caveats: >> >> 1. The ~/.config/guix/current profile really lives there. That is, >> unlike ~/.guix-profile, it=E2=80=99s not in /var/guix/profiles/per-= user. >> That could be an issue for cluster setups where home directories >> are not scanned by the Guix GC. Cluster folks, please tell me! > > What does that mean? We have a guix directory under $HOME/.config, > inside there's a symlink to /gnu/store/...-guix-. Does "really > lives there" mean the new profile is not a symlink but a concrete > directory or hard link? Please see how ~/.guix-profile and /var/guix/profiles/per-user/$USER/guix-profile work together. Basically generations show up in /var/guix/profiles, whereas ~/.guix-profile is a fixed symlink. >> 3. C++ code is not built. I wonder which will come first: getting rid >> of the C++ code, or building it? :-) >> > In the future world, how do we update guix daemon? Is't still running > guix pull && guix package -u under root user? In the future world, =E2=80=98guix pull=E2=80=99 updates everything: client= -side and daemon. Currently it=E2=80=99s still client-side only. HTH! Ludo=E2=80=99.