public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "byrnejb@harte-lyne.ca" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/18408] Provide software utility to permit user created custom locales
Date: Fri, 15 May 2015 14:47:00 -0000	[thread overview]
Message-ID: <bug-18408-716-UcD4EaULoQ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18408-716@http.sourceware.org/bugzilla/>

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

--- Comment #7 from James B. Byrne <byrnejb@harte-lyne.ca> ---
(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.

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

  parent reply	other threads:[~2015-05-15 14:47 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13 14:04 [Bug localedata/18408] New: " byrnejb@harte-lyne.ca
2015-05-13 14:28 ` [Bug localedata/18408] " myllynen at redhat dot com
2015-05-13 14:39 ` schwab@linux-m68k.org
2015-05-13 15:03 ` byrnejb@harte-lyne.ca
2015-05-13 15:57 ` byrnejb@harte-lyne.ca
2015-05-15 12:31 ` myllynen at redhat dot com
2015-05-15 12:47 ` fweimer at redhat dot com
2015-05-15 14:47 ` byrnejb@harte-lyne.ca [this message]
2015-05-15 15:52 ` carlos at redhat dot com
2015-05-15 17:40 ` byrnejb@harte-lyne.ca
2015-05-16 10:11   ` Keld Simonsen
2015-05-15 17:40 ` byrnejb@harte-lyne.ca
2015-05-15 22:35 ` byrnejb@harte-lyne.ca
2015-05-15 22:35 ` carlos at redhat dot com
2015-05-15 22:35 ` carlos at redhat dot com
2015-05-15 22:35 ` byrnejb@harte-lyne.ca
2015-05-15 22:36 ` byrnejb@harte-lyne.ca
2015-05-15 22:36 ` byrnejb@harte-lyne.ca
2015-05-15 22:36 ` carlos at redhat dot com
2015-05-15 22:36 ` byrnejb@harte-lyne.ca
2015-05-15 22:36 ` carlos at redhat dot com
2015-05-15 22:36 ` joseph at codesourcery dot com
2015-05-15 22:36 ` carlos at redhat dot com
2015-05-16 10:17 ` keld at keldix dot com
2015-06-22 13:27 ` myllynen at redhat dot com
2015-06-22 13:27 ` myllynen at redhat dot com
2015-06-22 21:31 ` byrnejb@harte-lyne.ca
2015-06-22 21:31 ` myllynen at redhat dot com
2015-06-23 15:40 ` maiku.fabian at gmail dot com
2015-07-11 19:50 ` neleai at seznam dot cz
2015-08-27 22:00 ` [Bug locale/18408] " jsm28 at gcc dot gnu.org
2016-05-16 21:46 ` carlos at redhat dot com
2016-05-16 21:46 ` [Bug core/18408] " gobisha6355 at gmail dot com
2017-05-06  0:56 ` [Bug locale/18408] " carlos at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-18408-716-UcD4EaULoQ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).