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: Thu, 01 Oct 2015 20:06:00 -0400 Message-ID: <87lhbmqglz.fsf@netris.org> References: <1443736716-8578-1-git-send-email-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]:45392) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zhnrp-00016t-Ec for guix-devel@gnu.org; Thu, 01 Oct 2015 20:06:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zhnrk-0000Ov-LX for guix-devel@gnu.org; Thu, 01 Oct 2015 20:06:29 -0400 In-Reply-To: <1443736716-8578-1-git-send-email-ludo@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22's\?\= message of "Thu, 1 Oct 2015 23:58:34 +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 Ludovic Court=C3=A8s writes: > So, below are a couple of patches implementing ideas that were discussed = here > and on IRC to improve the locale mess. > > The first patch adds the 'GUIX_LOCPATH' environment variable, the idea be= ing > that on foreign distros, users could set this variable instead of 'LOCPAT= H', > and the host distro's programs wouldn't break. > > The second patch was suggested by Mark. It basically adds "/2.22" to eve= ry > directory name specified in LOCPATH, as well as to the default locale > directory. The idea here is that libc would only stumble on compatible > locale data. > > Actually with that second patch, I think 'GUIX_LOCPATH' is unneeded, beca= use > effectively Guix's libc would already be interpreting 'LOCPATH' different= ly. > So my inclination would be to apply only the second one. > > Thoughts? For compatibility reasons, I think we should add "/2.22" _only_ to the entries of GUIX_LOCPATH. IMO, it's unwise to change the meaning of LOCPATH. Some programs, build systems, or user scripts might use "localedef" in a directory, set LOCPATH to that directory, and expect it to work. Mark