On 12/02/2019 17:10, Pierre Labastie via lfs-dev wrote:
First:
localedef -i POSIX -f UTF-8 C.UTF-8
generates warnings and has exit code 1! So it is not
suitable for scripting (at least with "set -e").
Looking at what debian does, they have a patch to generate
a file named "C" in localedata/locales. While the "POSIX" file
shipped with glibc contains only the ASCII characters, the "C"
file generated by debian contains a lot more characters.
So we should test whether the locale generated from "POSIX"
is enough for the Gjs test suite. Otherwise, it is not worth adding
it. If used, the full command (for scripting) should be:
localedef --quiet -i POSIX -f UTF-8 C.UTF-8 || true
note that --quiet prevents warnings to be generated, yet
the exit code is 1.
Pierre
Replying myself:
Discussion about including C.UTF-8 in upstream glibc:
https://sourceware.org/bugzilla/show_bug.cgi?id=17318
Debian patch:
https://salsa.debian.org/glibc-team/glibc/blob/sid/debian/patches/localedata/locale-C.diff
Fedora patch:
https://src.fedoraproject.org/rpms/glibc/blob/0457f649e3fe6299efe384da13dfc923bbe65707/f/glibc-c-utf8-locale.patch
They don't seem to agree totally...
Pierre
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
