From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH Date: Sun, 04 Oct 2015 12:56:55 -0400 Message-ID: <87fv1qvag8.fsf@netris.org> References: <1443736716-8578-1-git-send-email-ludo@gnu.org> <87oagfrq41.fsf@mdc-berlin.de> <87mvvzrpsf.fsf@mdc-berlin.de> <87bnce7r1j.fsf@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]:55948) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zimbf-0000JB-KU for guix-devel@gnu.org; Sun, 04 Oct 2015 12:57:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zimb8-0006PP-Jr for guix-devel@gnu.org; Sun, 04 Oct 2015 12:57:23 -0400 In-Reply-To: <87bnce7r1j.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 04 Oct 2015 14:32:24 +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: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: guix-devel@gnu.org, beffa@ieee.org ludo@gnu.org (Ludovic Court=C3=A8s) writes: > So with current =E2=80=98core-updates=E2=80=99, someone on a =E2=80=9Cfor= eign distro=E2=80=9D needs to > do: > > guix package -i glibc-locales > export GUIX_LOCPATH=3D$HOME/.guix-profile/lib/locale/2.22 > > Note the extra =E2=80=9C/2.22=E2=80=9D, which comes from commit f2d7bbb. = This is a bit > of an annoyance for end users, but the point is that eventually this > would allow us to recommend things like: > > export GUIX_LOCPATH=3D$HOME/.guix-profile/lib/locale/2.22:$HOME/.guix-p= rofile/lib/locale/2.23 > > The only question is whether having the =E2=80=9C/2.22=E2=80=9D prefix by= default is a > good idea. Opinions? I think the "/2.22" suffix will be needed to prevent another awkward transition the next time glibc makes an incompatible change to their locales. Suppose that 2.23 makes another incompatible change. After that, many Guix systems will have a mixture of software linked with glibc-2.22 and glibc-2.23. One question: when this happens, do we have a mechanism for automatically setting GUIX_LOCPATH to: $HOME/.guix-profile/lib/locale/2.22:$HOME/.guix-profile/lib/locale/2.23 or will that have to be done manually? Mark