From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57166) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gFysa-0008T4-4b for guix-patches@gnu.org; Fri, 26 Oct 2018 05:58:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gFysV-00086i-44 for guix-patches@gnu.org; Fri, 26 Oct 2018 05:58:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:38971) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gFysV-00086e-09 for guix-patches@gnu.org; Fri, 26 Oct 2018 05:58:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1gFysT-0003Yu-VP for guix-patches@gnu.org; Fri, 26 Oct 2018 05:58:02 -0400 Subject: [bug#33111] [PATCH 0/3] Have the binary tarball populate ~root/.config/guix/current Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <20181021204506.1978-1-ludo@gnu.org> <87bm7hsrjt.fsf@gnu.org> <87a7n15l1g.fsf@elephly.net> Date: Fri, 26 Oct 2018 11:57:02 +0200 In-Reply-To: <87a7n15l1g.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 26 Oct 2018 07:33:47 +0200") Message-ID: <871s8dni8h.fsf@gnu.org> 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: Ricardo Wurmus Cc: 33111@debbugs.gnu.org Hello! Ricardo Wurmus skribis: >>> 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=98= glibc-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 With a what? :-) > I=E2=80=99m not sure I understand why ~root/.config/guix/current would be= the > 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 pac= kage. > > 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? It=E2=80=99s inelegant and just a partial solution because =E2=80=98guix pu= ll=E2=80=99 won=E2=80=99t upgrade it. It would also show up in =E2=80=98guix pull -l=E2=80=99, which= isn=E2=80=99t great. > 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, = but I > think in the special case of =E2=80=9Cguix pull=E2=80=9D it could be a re= asonable > compromise / an acceptable exception. What do you think? I share your concern but I can=E2=80=99t think of a good solution. Since =E2=80=98glibc-locales=E2=80=99 is big (520M on disk!) and more than = what people need, we certainly don=E2=80=99t want to pull it. So we=E2=80=99d be pulli= ng =E2=80=98glibc-utf8-locales=E2=80=99 as we currently do, knowing that it=E2= =80=99s an arbitrary choice of locales that favors Western countries. Let=E2=80=99s say we arrange so =E2=80=98guix=E2=80=99 is wrapped such that= GUIX_LOCPATH points to a bundled =E2=80=98glibc-utf8-locales=E2=80=99. That solves the problem= for the =E2=80=98guix=E2=80=99 command, but it doesn=E2=80=99t solve it for other p= ackages installed with =E2=80=98guix=E2=80=99: users would still need to install =E2=80=98gli= bc-utf8-locales=E2=80=99. A =E2=80=9Cproper fix=E2=80=9D might be to add =E2=80=98glibc-utf8-locales= =E2=80=99 to ~root/.guix-profile in the binary tarball. However, as I wrote, it would require us to improve =E2=80=98guix pack=E2=80=99 so it can populate = several profiles, which is not trivial and probably not very useful in other situations. On the bright side, =E2=80=98guix=E2=80=99 gives users the command to copy/= paste to install locales (commit 26db747a863b08ebcfd630cce635be86c23d829d), so it=E2=80=99s not that bad. :-) Also, we could have the install script run =E2=80=98guix package -i glibc-utf8-locales=E2=80=99 automatically. Thoughts? Thanks for your feedback! Ludo=E2=80=99.