Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-06 Thread Federico Beffa
On Mon, Oct 5, 2015 at 11:09 PM, Ludovic Courtès wrote: > Federico Beffa skribis: > >> I'm wondering if it would be better to point GUIX_LOCPATH to >> >> export GUIX_LOCPATH=$HOME/.guix-profile/lib/locale >> >> and have 'glibc' itself to append it's own version

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-05 Thread Ludovic Courtès
Federico Beffa skribis: > On Mon, Oct 5, 2015 at 4:35 PM, Ludovic Courtès wrote: >> Mark H Weaver skribis: >> >>> l...@gnu.org (Ludovic Courtès) writes: >>> So with current ‘core-updates’, someone on a “foreign distro” needs to do:

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-05 Thread Ludovic Courtès
Federico Beffa skribis: > I'm wondering if it would be better to point GUIX_LOCPATH to > > export GUIX_LOCPATH=$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)

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-05 Thread Ludovic Courtès
Mark H Weaver skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> So with current ‘core-updates’, someone on a “foreign distro” needs to >> do: >> >> guix package -i glibc-locales >> export GUIX_LOCPATH=$HOME/.guix-profile/lib/locale/2.22 >> >> Note the extra “/2.22”,

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-05 Thread Ludovic Courtès
Mark H Weaver skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> After a lot more thought, I changed my mind. >> >> I realized that with the patch at >> , it’s OK to >> have, say, >> >> >>

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-05 Thread Federico Beffa
On Mon, Oct 5, 2015 at 4:35 PM, Ludovic Courtès wrote: > Mark H Weaver skribis: > >> l...@gnu.org (Ludovic Courtès) writes: >> >>> So with current ‘core-updates’, someone on a “foreign distro” needs to >>> do: >>> >>> guix package -i glibc-locales >>> export

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-04 Thread Ludovic Courtès
Daniel Pimentel skribis: > I added 'export LC_ALL="C"' in my ~.bashrc. > > I'll to do upgrade and report it. With LC_ALL=C, one sidesteps the problem. For real testing, you need to use LC_ALL=pt_BR.utf8 or something like that. Ludo’.

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-04 Thread Mark H Weaver
l...@gnu.org (Ludovic Courtès) writes: > So with current ‘core-updates’, someone on a “foreign distro” needs to > do: > > guix package -i glibc-locales > export GUIX_LOCPATH=$HOME/.guix-profile/lib/locale/2.22 > > Note the extra “/2.22”, which comes from commit f2d7bbb. This is a bit > of an

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-04 Thread Mark H Weaver
l...@gnu.org (Ludovic Courtès) writes: > After a lot more thought, I changed my mind. > > I realized that with the patch at > , it’s OK to > have, say, > > >

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-03 Thread Ludovic Courtès
After a lot more thought, I changed my mind. I realized that with the patch at , it’s OK to have, say, LOCPATH=$HOME/.guix-profile/lib/locale/2.22:$HOME/.guix-profile/lib/locale/2.23 That way, programs will pick locale data that is

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-03 Thread Daniel Pimentel
On 2015-10-03 19:20, l...@gnu.org wrote: After a lot more thought, I changed my mind. I realized that with the patch at , it’s OK to have, say, LOCPATH=$HOME/.guix-profile/lib/locale/2.22:$HOME/.guix-profile/lib/locale/2.23 That

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-02 Thread Ludovic Courtès
Mark H Weaver skribis: > 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

[PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-01 Thread Ludovic Courtès
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 being that on foreign distros, users could set this variable instead of 'LOCPATH', and the host distro's

Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH

2015-10-01 Thread Mark H Weaver
Ludovic Courtès 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 being > that on foreign distros, users could set this variable