On Sat, 09 Aug 2014, Paul Eggert wrote:
This harmless bug was introduced in release 2014f, which distributed leapseconds.awk in both the code and the data tarballs. It's code, so it should be in the code tarball.
I'd prefer to let tzdata contain all zic inputs, and all scripts used to help maintain the zic inputs. If leapseconds.awk is not in tzdata then it's unnecessarily difficult to re-generate leapseconds from leap-seconds.list, or to verify that leapseconds and leap-seconds.list are in sync. The question should not be "is it code?", but rather "is it necessary or useful to people who use tzdata but don't use tzcode?" I think that tzcode should contain all code that's intended to be installed on a target system, but it's not necessary for it to contain scripts that are intended to be used only by maintainers, and not installed for use by end users. While we are talking about what belongs in each tarball, I'd also like to ask that the NEWS file be included in tzdata. --apb (Alan Barrett)