mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
	musl@lists.openwall.com, tz@iana.org
Subject: Re: [musl] Re: [tz] [musl] Re: Weird PST8PDT and EST5EDT behavior on Alpine Linux
Date: Tue, 5 Mar 2024 20:54:15 -0500	[thread overview]
Message-ID: <20240306015415.GG4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <e16c77f0-415c-40c7-a0f5-48aff0b9ac53@cs.ucla.edu>

On Tue, Mar 05, 2024 at 04:47:02PM -0800, Paul Eggert wrote:
> On 3/5/24 12:12, Rich Felker via tz wrote:
> >Yes, it's not clear to me (POSIX doesn't seem to specify) what the
> >default rules should be when none are specified. However, it is clear
> >that these strings meet the syntax for the POSIX TZ form, and thus
> >musl does not attempt to interpret them as filenames, which could
> >result in behavior contrary to the specified meaning.
> 
> Although TZDB interprets them as filenames, that is OK because the
> TZDB filenames have the specified meaning. Each TZDB Zone whose name
> has the form of a POSIX.1-2017 TZ string implements a set of
> transitions compatible with the corresponding POSIX TZ setting.
> 
> Long ago that wasn't the case: there were Zones like "GMT-12" that
> weren't compatible with POSIX even though their names took the POSIX
> forms. But that bug was fixed decades ago, in tzdata 94d
> (1994-02-24), and we no longer need to worry about that possibility.

Interesting idea we could consider: if the TZ string matches POSIX
format for a zone with DST but without any rule portion, load a file
and accept it if the zones are consistent (all name/offset pairs
match) -- so that it's effectively just defining the transition date
rules.

Rich

      reply	other threads:[~2024-03-06  1:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87edcqv69m.fsf@hope.eyrie.org>
2024-03-05  3:52 ` [musl] Re: [tz] " Đoàn Trần Công Danh
2024-03-05  4:31   ` Paul Eggert
2024-03-05 20:12   ` Rich Felker
2024-03-05 20:56     ` Russ Allbery
2024-03-05 21:37       ` [musl] Re: [tz] [musl] " Guy Harris
2024-03-05 22:03         ` Russ Allbery
2024-03-05 22:12           ` Guy Harris
2024-03-05 22:31             ` Russ Allbery
2024-03-06 15:39               ` James Cloos
2024-03-08 17:46                 ` [musl] Re: [tz] " Paul Eggert
2024-03-08 19:02                   ` Rich Felker
2024-03-09  0:09                     ` James Cloos
2024-03-09  1:57                     ` [musl] Re: [tz] [musl] " Guy Harris
2024-03-08 18:39                 ` Guy Harris
2024-03-08 19:05                   ` [musl] Re: [tz] " Paul Eggert
2024-03-09  0:03                   ` [musl] " James Cloos
2024-03-06  0:47     ` [musl] Re: [tz] " Paul Eggert
2024-03-06  1:54       ` Rich Felker [this message]

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=20240306015415.GG4163@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=congdanhqx@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=musl@lists.openwall.com \
    --cc=tz@iana.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).