[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH
From: |
Ludovic Courtès |
Subject: |
Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH |
Date: |
Mon, 05 Oct 2015 16:35:20 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Mark H Weaver <address@hidden> skribis:
> address@hidden (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 annoyance for end users, but the point is that eventually this
>> would allow us to recommend things like:
>>
>> export
>> GUIX_LOCPATH=$HOME/.guix-profile/lib/locale/2.22:$HOME/.guix-profile/lib/locale/2.23
>>
>> The only question is whether having the “/2.22” 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.
Yes. But we could just as well have ‘glibc-utf8-locales’ where
everything is in lib/locale directly, and ‘glibc-transition-locales’
where things are under lib/locale/2.22 and lib/locale/2.23. Dunno.
> 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?
Unless glibc is in the profile, that has to be done manually.
Ludo’.
- Re: Preparing for the libc/locale upgrade, (continued)
- Re: Preparing for the libc/locale upgrade, Federico Beffa, 2015/10/08
- Re: Preparing for the libc/locale upgrade, Konrad Hinsen, 2015/10/08
- Re: Preparing for the libc/locale upgrade, Ludovic Courtès, 2015/10/08
- Re: Preparing for the libc/locale upgrade, Federico Beffa, 2015/10/08
- [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Ludovic Courtès, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Ricardo Wurmus, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Ricardo Wurmus, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Ludovic Courtès, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Mark H Weaver, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH,
Ludovic Courtès <=
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Federico Beffa, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Ludovic Courtès, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Ludovic Courtès, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Federico Beffa, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Mark H Weaver, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Ludovic Courtès, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Ludovic Courtès, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Mark H Weaver, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Ludovic Courtès, 2015/10/08
- Re: [PATCH 0/2] Avoiding incompatible locale data in LOCPATH, Daniel Pimentel, 2015/10/08