Iain Arnell wrote: > we can't simply repackage T:OTZ:D from CPAN as it >contains precompiled tz files.
I don't see why you can't. The tz files are platform-neutral. > And it doesn't make sense for use to >rebuild the whole thing from source as we already have a tzdata >package that contains exactly the same data and is updated regularly. I thought about that. I think the clever way to package it is to make the package depend on the existing tzdata package, not include the files that are identical to those in tzdata, and have its installation script set up hard links from the tzdata files. That would give you a completely normal version of the Perl module, which finds the tz files in the Perl module tree as normal, while actually sharing storage with the tz files that libc uses. You must, of course, ensure that the tz files are actually bit-for-bit identical in order to make this trick valid. They will be as long as you're using the Olson zic to generate your tzdata package. Anyway, to answer your direct question: no, the code that builds a T:OTZ:D release is not public. I'm approaching switching to git, at which point I'll most likely publish repos, which in the T:OTZ:D case will include the automatic build code. -zefram
