From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44919) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gFum2-00079x-DT for guix-patches@gnu.org; Fri, 26 Oct 2018 01:35:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gFuly-0005Vn-Dq for guix-patches@gnu.org; Fri, 26 Oct 2018 01:35:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:38841) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gFuly-0005Uu-AB for guix-patches@gnu.org; Fri, 26 Oct 2018 01:35:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gFuly-0005ZE-0Y for guix-patches@gnu.org; Fri, 26 Oct 2018 01:35:02 -0400 Subject: [bug#33111] [PATCH 0/3] Have the binary tarball populate ~root/.config/guix/current Resent-Message-ID: References: <20181021204506.1978-1-ludo@gnu.org> <87bm7hsrjt.fsf@gnu.org> From: Ricardo Wurmus In-reply-to: <87bm7hsrjt.fsf@gnu.org> Date: Fri, 26 Oct 2018 07:33:47 +0200 Message-ID: <87a7n15l1g.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: 33111@debbugs.gnu.org Hi Ludo, >> These patches address this by having the binary tarball populate >> ~root/.config/guix/current like =E2=80=98guix pull=E2=80=99 does. >> >> There=E2=80=99s one downside though: with the last patch, the =E2=80=98g= libc-utf8-locales=E2=80=99 >> is no longer included because ~root/.config/guix/current would be the >> wrong place for it. Consequently, users have to explicitly install it >> in ~root/.guix-profile and set GUIX_LOCPATH accordingly. > > Any comments? Ricardo? Thank you for fixing this very confusing situation! It is very good to start out with a I=E2=80=99m not sure I understand why ~root/.config/guix/current would be t= he wrong place for the locales package. It is true that this directory is for Guix only, but users don=E2=80=99t need to know about the locales packa= ge. Is it a problem to install the locales package alongside Guix in the =E2=80=9Cguix pull=E2=80=9D profile, or is it just inelegant? I think it would be unfortunate if older versions of Guix would stop working or report warnings when they are used in combination with a separately managed profile containing the locales. The locales need to match the glibc version that the program is linked with, so I would prefer if we could keep Guix and the locales together. You know that I find the separation of glibc-locales to be an unfortunate tradeoff, which makes using Guix on foreign distros a little less convenient. While I think that this patch set is a definite improvement over the current situation, I would be sad to see the locales separated and become a source of frustration or confusion. Is there something we can do about this? Would it be acceptable to add glibc-locales as an explicit input to the result of =E2=80=9Cguix pull=E2= =80=9D? I understand that we don=E2=80=99t usually add glibc-*locales as an input, bu= t I think in the special case of =E2=80=9Cguix pull=E2=80=9D it could be a reas= onable compromise / an acceptable exception. What do you think? -- Ricardo