Yes. <br><br>Packagers: Please keep it compatible with what iana tarball updaters (such as tzupdater, various language packages) expect but as a directory: minimal changes maximize portable reusability and minimize support/maintenance for everyone. And please don't collide file hierarchy by breaking existing conventions but make it sensible like:<br><br>/usr/share/iana-tzinfo-src/latest<br>--symlink-><br>/usr/share/iana-tzinfo-src/20NNz<br><br>This makes it unambiguous about what it is what and allows for rolling-release upgrades without breaking production processes that cannot survive system "static" shared data files randomly disappearing beneath them.<br><br>Barry Allard<br><div class="gmail_quote"><div dir="ltr">On Mon, May 22, 2017 at 10:54 AM Brian Inglis <<a href="mailto:Brian.Inglis@systematicsw.ab.ca">Brian.Inglis@systematicsw.ab.ca</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2017-05-22 07:03, Patsy Franklin wrote:<br>
> I'd appreciate community input on this plan. Ideally if others decide<br>
> to also ship a similar subpackage we can use a common naming<br>
> convention and install directory.<br>
><br>
> We are planning to ship a new subpackage for users who want to have<br>
> access to the raw zone data files e.g. leapseconds, and in a<br>
> pre-determined install location e.g. /usr/share/zoneinfo/zonedata/.<br>
<br>
How about using /usr/share/tzdata{,-src}/ maybe with subdirectories<br>
tzdata-2017b, etc.<br>
<br>
> The raw zone data is useful for users designing their own interfaces<br>
> on top of this data. The broadest flexibility is offered by the raw<br>
> zone data, and while the compiled binary data is versioned and more<br>
> stable, some users have expressed a request for the raw zone data.<br>
> The understanding is that the raw zone data format may change.<br>
><br>
> In summary:<br>
> Our current plan is to use -zonedata in naming the subpackage, For<br>
> example, tzdata-zonedata-2017b-1.el7.<br>
<br>
How about tzdata-src-2017b...?<br>
<br>
> We plan to install the files in this subpackage under<br>
> /usr/share/zoneinfo/zonedata/.<br>
<br>
Adding zonedata does not add any useful information about the contents<br>
and storing under /usr/share/zoneinfo/ could be confusing as there are<br>
already subdirectories posix and right holding copies of standard and<br>
leapsecond compensated binary data files, so TZ=posix/... and<br>
TZ=right/... are valid zones, and users may expect something similar to<br>
happen using TZ=zonedata/... which would be unfortunate.<br>
<br>
> Just as an example we would ship the following files:<br>
> LICENSE<br>
> version<br>
> africa<br>
> antarctica<br>
> asia<br>
> australasia<br>
> europe<br>
> northamerica<br>
> southamerica<br>
> pacificnew<br>
> etcetera<br>
> backward<br>
> systemv<br>
> factory<br>
> backzone<br>
> iso3166.tab<br>
> leapseconds<br>
> leap-seconds.list<br>
> zone1970.tab<br>
> zone.tab<br>
<br>
README, CONTRIBUTING, NEWS, and Theory should be included, also<br>
tz-how-to.html which documents how to define and use the sources.<br>
leap-seconds.list should be a (symbolic?) link to the canonical file<br>
version leap-seconds.<timestamp> e.g. leap-seconds.3692908800.<br>
<br>
--<br>
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada<br>
</blockquote></div>