<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Oct 27, 2015 at 7:40 AM, Guy Harris <span dir="ltr"><<a href="mailto:guy@alum.mit.edu" target="_blank">guy@alum.mit.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On Oct 26, 2015, at 2:50 PM, Bradley White <<a href="mailto:bww@acm.org">bww@acm.org</a>> wrote:<br>> On Sun, Oct 25, 2015 at 2:30 PM, Guy Harris <<a href="mailto:guy@alum.mit.edu">guy@alum.mit.edu</a>> wrote:<br>
>> Is this just something to let people know whether they have an up-to-date version of the tzdb files or not?<br>
><br>
> Yes, although I think of it simply as let people know what version of a tzdb file they have. (Whether that is the latest version is a separate question.)<br>
<br>
</span>Which version they have, or which version of the IANA tzdb the version they have is based on? :-)<br></blockquote><div><br></div><div>The version of the data file that was passed to zic to produce the zoneinfo file in question.</div><div><br></div><div>(If someone downstream wants to modify data files and recompile them, then sub-versioning is up to them.)</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">> I would even propose an additional self-identification step: include the zone name in tzdb file.<br>
<br>
</span>Which zone name is "the" zone name? The zone name on the system on which zic was run?<br></blockquote><div><br></div><div>The zone name is the Zone field from the data file used to produce the zoneinfo file.</div><div><br></div><div>(There would be a question about how to handle Links.)</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">> Then you could tell, for example, where /etc/localtime came from.<br>
<br>
</span>Well, on my system, it came from a symlink() call:<br>
<br>
$ ls -l /etc/localtime<br>
lrwxr-xr-x 1 root wheel 39 Oct 10 21:20 /etc/localtime -> /usr/share/zoneinfo/America/Los_Angeles<br></blockquote><div><br></div><div>And on others it is a copy. It seems preferable to have the data be self identifying rather than assuming anything about symlinks.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">although if I were traveling there would be more than such symlink() call, one made whenever the machine changes what tzdb zone it's in (I checked "Set time zone automatically using current location" in the "Time Zone" subpane of the "Date & Time" pane of System Preferences"). Should the code making those symlink() calls also write to each compiled tzdb file under /usr/share/zoneinfo, updating the zone name?</blockquote><div><br></div><div>No, the zone name in any zoneinfo file would be constant.</div><div><br></div><div>As an example, perhaps we could then see:</div><div><br></div><div><div><font face="monospace, monospace">$ file /etc/localtime </font></div><div><font face="monospace, monospace">/etc/localtime: timezone data, <b>zone America/New_York</b>, <b>release 2015f-0ubuntu0.14.04</b>, version 2, 4 gmt time flags, 4 std time flags, no leap seconds, 235 transition times, 4 abbreviation chars</font></div></div></div></div></div>