Andreas Enge <andr...@enge.fr> skribis: > The code of glibc states > ;; Installing a locale archive with all the locales is to > ;; expensive (~100 MiB), so we rely on users to install the > ;; locales they really want. > But how do I do that? I wondered if there was an additional "locale" output > of glibc, but there is not. > > $ guix package -A locale > does not return anything useful. > > There is a section 6.2.6 in the manual, but it only speaks about GSD, > not about Guix inside other systems.
Right, Mark reported it as well. The basic idea is that it’s up to you to define $LOCPATH and have it point to a place that contains locale data (info "(libc) Locale Names"). But I think we could provide a ‘glibc-locales’ package (110 MiB) for those in search of a quick fix on foreign distros. (Time passes...) Commit aee6180c adds ‘glibc-locales’. You can install it and do: export LOCPATH=$HOME/.guix-profile/share/locale though that’s not the most efficient approach space-wise. I would instead recommend using your host libc’s locale data, which should be compatible; something like that (untested): export LOCPATH=/usr/share/locale Last, commit d6718df of ‘core-updates’ adds a search path specification for ‘LOCPATH’. (Not really useful for profiles since one would need to explicitly install glibc in their profile to get the message about ‘LOCPATH’.) Ludo’.
