[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Preparing for the libc/locale upgrade
From: |
Mark H Weaver |
Subject: |
Re: Preparing for the libc/locale upgrade |
Date: |
Tue, 29 Sep 2015 10:32:08 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Federico Beffa <address@hidden> writes:
> address@hidden (Ludovic Courtès) writes:
>
> [...]
>
>> Consequences for Guix on foreign distros:
>>
>> • If the host distro provides binaries that use libc < 2.22 and you
>> use a mixture of Guix-provided and distro-provided programs, this is
>> pretty bad.
>>
>> Solution: unset LOCPATH and say goodbye to locales for Guix-provided
>> packages (setting LOCPATH=$HOME/.guix-profile/lib/locale would break
>> all the distro-provided programs), or use exclusively Guix-provided
>> programs, or use the “C” locale.
>
> Does this means that Guix on other distributions is no longer of
> interest to the Guix project and it is essentially unsupported?
>
> Or is this a transitory situation and an acceptable solution is being
> worked on?
I think I know a workaround: leave LOCPATH unset, and make
/run/current-system/locale a symlink to freshly generated locales for
glibc 2.22. Guix-compiled software is configured to look for locales
there if LOCPATH is unset.
Mark
- Re: Preparing for the libc/locale upgrade,
Mark H Weaver <=