Import the C.UTF-8 locale to glibc |
||
Issue descriptionFollowing the feature requests against upstream glibc [1], a UTF-8 locale seems highly requested, and distros like Fedora and CoreOS have added their own C.UTF-8 locale patch. [2][3] Can we import their patch? [1] https://sourceware.org/bugzilla/show_bug.cgi?id=17318 [2] http://pkgs.fedoraproject.org/cgit/rpms/glibc.git/tree/glibc-c-utf8-locale.patch [3] https://github.com/coreos/coreos-overlay/pull/2194
,
Jan 6 2017
NVM. You are right it probably doesn't make sense for chromiumos anyway.
,
Jan 20 2017
Coming back to this after a while. vapier@, what do you think of importing the c.utf8 patch but make it USE flag guarded? As glibc comes within the toolchain, it's difficult to patch it in board overlays.
,
Jan 20 2017
a USE flag guard wouldn't help since, as you say, toolchains can't change on a per-board basis the previous question still stands though ... what/why do you need this in CrOS ?
,
Jan 20 2017
> toolchains can't change on a per-board basis Ah, right. > what/why do you need this in CrOS ? For Lakitu, we want to have a basic utf8 locale (many apps want/assume default utf8 locale) and the C.utf-8 I mentioned earlier seems the most reasonably for it's minimal, and it applies to glibc, which we get from cros. More background can be found in b/31761738 and b/32920411.
,
Jan 23 2017
vapier@, since we can't patch glibc on a per-board basis, I am thinking of adding lakitu specific package, say, glibc-utf8-locale, which just runs `localedef` and installs a locale. Do you see any problem with that? |
||
►
Sign in to add a comment |
||
Comment 1 by vapier@chromium.org
, Jan 6 2017