[Bug localedata/18408] Provide software utility to permit user created custom locales

["carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=18408

Carlos O'Donell <carlos at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |carlos at redhat dot com

--- Comment #8 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to James B. Byrne from comment #7)
> (In reply to Florian Weimer from comment #6)
> > (In reply to James B. Byrne from comment #3)
> > > But not on RHEL6 which is what an end user, who only wants to change the
> > > date and time format, is likely to know of or to check.
> > 
> > I believe on Red Hat Enterprise Linux, glibc updates will wipe out
> > user-defined locales, so using this functionality might not be a good idea
> > after all.
> 
> The request is for a utility to ease the production of custom locale files
> not for modifications to the standard distributed locale files.  Although
> that necessarily could be a consequence.  I have created several custom
> locales on CentOS-6 and 7 systems and these have never been disturbed by
> updates to glibc.  I cannot see how updates to glibc could have that effect
> as customised locales are unknown, and therefore invisible, to the glibc
> update process.
> 
> I suppose if the changes to glibc involved a complete restructuring of the
> directory locations then that might have the effect of disabling any
> customised locales, but I cannot see that destroying them.

User locales can be installed into two locations. Directly as files, where they
can be parsed, or installed into the locale archive to loaded directly into
every application for faster usage.

The general problem is that distributions, at least in Fedora and RHEL,
overwrite the locale archive when glibc is upgraded.

Either way, this is a Fedora or RHEL issue and not a generic upstream issue.

At the very least we need:

* localedef documentation.
* examples using localedef to install a locale to the locale archive.

-- 
You are receiving this mail because:
You are on the CC list for the bug.