This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Removing locale timezone information

On 13/08/15 07:37, Keld Simonsen wrote:
> On Wed, Aug 12, 2015 at 11:06:16AM -0400, Zack Weinberg wrote:
>> On Wed, Aug 12, 2015 at 10:08 AM,  <> wrote:
>>> My impression is that timezone changes are normally announced in due time
>>> so that they can be included in normal glibc release schedule, which
>>> I think is about twice a year, but irregulary. I have not been down into
>>> the data, tho.
>> Sadly, as pointed out by others, this is not so.
>> Keld, would your use cases be satisfied if each glibc locale (for
>> which this makes sense) specified a default *Olsen* timezone?  I think
>> that might be a way to get what you want while avoiding the problems
>> everyone else is bringing up.
> As others has pointed out, there are a number of cases where time zone changes
> havd been made with very short notice. I was talking about the normal case,
> meaning the majority of cases. I need to go deeper into the data
> to see for myself if I should consider myself being wrong. But just mentioning a few cases
> do not make my statement false. And my general knowledge
> of timezone changes are that they are not frequent. In EU and in the USA and Canada
> and big countries in Asia there have been few changes AFAIK in the last few decades, but 
> of cause there are many countries and a few changes here and there all adds up.
> I will have a look, as suggested.

I can remember having to ship a tzdata package fast due to last minute
DST changes for somewhere in the USA.  Even if it is the minority of
cases, this makes using glibc for this information rather than tzdata
very difficult for a Linux distribution.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]