mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Russ Allbery <eagle@eyrie.org>
To: Guy Harris <gharris@sonic.net>
Cc: Rich Felker <dalias@libc.org>,  Ian Abbott via tz <tz@iana.org>,
	musl@lists.openwall.com
Subject: [musl] Re: [tz] [musl] Re: Weird PST8PDT and EST5EDT behavior on Alpine Linux
Date: Tue, 05 Mar 2024 14:31:33 -0800	[thread overview]
Message-ID: <87msrcpayi.fsf@hope.eyrie.org> (raw)
In-Reply-To: <77902F3C-198B-49BD-AB75-383A7FF45548@sonic.net> (Guy Harris's message of "Tue, 5 Mar 2024 14:12:29 -0800")

Guy Harris <gharris@sonic.net> writes:
> On Mar 5, 2024, at 2:03 PM, Russ Allbery <eagle@eyrie.org> wrote:

>> It seems to support what I said: PST8PDT was supported, but :PST8PDT was not.

> Yes.  As I indicated, they didn't have tzdb code (if they did, that
> would be a surprise, as the tzdb project didn't exist in 1979/1980), and
> they didn't support any POSIX extensions to TZ (if they did, that would
> be a surprise as, at least according to
> https://en.wikipedia.org/wiki/POSIX, the first POSIX standard came out
> in 1988).

Ah, sorry, I had just misunderstood you.  Thank you for the confirmation
and reference!

Basically, to summarize, up until now I think it was possible to set TZ to
PST8PDT and have it work essentially everywhere, no matter how old the
edition of UNIX, thanks to the backward compatibility file in tzdata.  I
think musl may have been the first place where this broke somewhat
intentionally.  This is not a big deal and I'm not sure I'm arguing that
musl should change; I expect interfaces to change over time and it's
probably time to assume everyone supports the Olson identifiers.  But it
is a change in the portability landscape, if a minor one.  (Probably one
that's been around for a while and I just never noticed because I hadn't
been running the INN test suite on Alpine Linux.)

-- 
Russ Allbery (eagle@eyrie.org)             <https://www.eyrie.org/~eagle/>

  reply	other threads:[~2024-03-05 22:31 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 [this message]
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

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=87msrcpayi.fsf@hope.eyrie.org \
    --to=eagle@eyrie.org \
    --cc=dalias@libc.org \
    --cc=gharris@sonic.net \
    --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).