Tzdata2006b.tar.gz, tz32code2006b.tar.gz, and tz64code2006b.tar.gz
eggert at CS.UCLA.EDU
Tue Feb 21 21:05:49 UTC 2006
"Olson, Arthur David \(NIH/NCI\) [E]" <olsona at dc37a.nci.nih.gov> writes:
> The 32-bit code is there for folks who may need it; with providence,
> there will be little or no need to update it.
This means we'll need to update the instructions in tz-link.htm, which
currently say this:
gzip -dc tzcode*.tar.gz | tar -xf -
gzip -dc tzdata*.tar.gz | tar -xf -
and this won't work nicely, due to the two code tarballs overridding
The names tz32code2006b.tar.gz and tz64code2006b.tar.gz are a bit
confusing, since people might naturally get confused into thinking
that the tarballs are for 32-bit and 64-bit development platforms, or
for 32-bit and 64-bit runtime platforms, whereas neither is the case:
they are really for 32-bit and 64-bit tz files, which is a different
Here's an idea. How about if we rename tz32code2006b.tar.gz to
pre2038-tzcode2006b.tar.gz, and rename tz64code2006b.tar.gz back to
tzcode2006b.tar.gz? That way, I won't have to change tz-link.htm (so
it's less work for me :-), and also, users will be able to see more
clearly why one might prefer the current to the previous version.
Also, this naming convention fits in better with the recently-removed
'classictzcode' and 'classictzdata' convention.
If you still prefer the current naming style, please let me know, so
that I can propose a patch to tz-link.htm. Thanks.
More information about the tz