From mboxrd@z Thu Jan 1 00:00:00 1970 From: Federico Beffa Subject: Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH Date: Tue, 6 Oct 2015 08:29:41 +0200 Message-ID: References: <1443736716-8578-1-git-send-email-ludo@gnu.org> <87oagfrq41.fsf@mdc-berlin.de> <87mvvzrpsf.fsf@mdc-berlin.de> <87bnce7r1j.fsf@gnu.org> <87fv1qvag8.fsf@netris.org> <878u7h1izb.fsf@gnu.org> <87wpv16mzw.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]:57102) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjLkt-0001Sp-LU for guix-devel@gnu.org; Tue, 06 Oct 2015 02:29:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZjLks-0004cz-AB for guix-devel@gnu.org; Tue, 06 Oct 2015 02:29:43 -0400 In-Reply-To: <87wpv16mzw.fsf@gnu.org> 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: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: Guix-devel On Mon, Oct 5, 2015 at 11:09 PM, Ludovic Court=C3=A8s wrote: > Federico Beffa skribis: > >> I'm wondering if it would be better to point GUIX_LOCPATH to >> >> export GUIX_LOCPATH=3D$HOME/.guix-profile/lib/locale >> >> and have 'glibc' itself to append it's own version number to that >> string. In this way pre 2.22 programs (last official Guix(SD) release) >> would find pre-2.22 locale in '/$HOME/.guix-profile/lib/locale'. > > With the discussion on IRC following your message, I ended up going back > to the solution that appends /2.22 to the GUIX_LOCPATH entries > automatically: > > http://article.gmane.org/gmane.comp.gnu.guix.devel/12004 > > We=E2=80=99ll settle on that and declare the problem solved now. :-) > > Sorry for the hesitations. It=E2=80=99s one of these situations where we= have > conflicting principles: simplifying the users lives, and remaining close > to what upstream does. I think this is the right thing to do. It's not just about making the lives of users easier, but rather preventing that users will see their profile break after an update (when a new 'glibc' with incompatible locales will come out). IMO such a behavior would just be bad design. Thanks, Fede