This is the mail archive of the
mailing list for the glibc project.
Re: Removing locale timezone information
- From: "keld at keldix dot com" <keld at keldix dot com>
- To: pinskia at gmail dot com
- Cc: Marko Myllynen <myllynen at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, "libc-locales at sourceware dot org" <libc-locales at sourceware dot org>
- Date: Thu, 6 Aug 2015 20:06:11 +0200
- Subject: Re: Removing locale timezone information
- Authentication-results: sourceware.org; auth=none
- References: <556F23C9 dot 3030500 at redhat dot com> <20150603203430 dot GC15814 at www5 dot open-std dot org> <55715DB2 dot 2010500 at redhat dot com> <20150806175226 dot GD28963 at www5 dot open-std dot org> <EE629769-A7DF-42C3-B58D-C1F373D0F010 at gmail dot com>
On Thu, Aug 06, 2015 at 08:01:17PM +0200, firstname.lastname@example.org wrote:
> > Well, we always need to update glibc with the current stuff, that is normal
> > glibc maintenance.
> > We always need to change locales if the backgrund data changes.
> > For instance if Greece gets a new currency, we need to change that in our
> > locales. I thing tz data changes are not very frequent, but I may be wrong.
> > It has not changed for most of the European countries for many years.
> U.S. Timezones has changed in the last ten years due to a few different things. One is an addition of a leap second. Another was to daylight savings time (summer time) start/end date. And then there was Indiana Timezone changes due to deciding to have daylight savings time.
I think the level of changes in Europe are the same, only a few in a decade.
This can easily be managed by current glibc mantenence schedule, and distributin
maintenance schedule. Actually if Olson tz data is maintained in a distribution,
it would follow a similar schedule.
Anyway, are Olson tzdata used in GNU interfaces?