On Fri, Jan 31, 2003 at 12:32:57AM -0600, Dave Rolsky wrote: > On Thu, 30 Jan 2003, John Peacock wrote: > > > Dave Rolsky wrote: > > > I just checked in a lot of new/changed code under > > > modules/DateTime-TimeZone. This code actually seems to work, and provides > > > access to the complete Olson historical data, plus ongoing time zone > > > changes in the future. > > > > t/01load.....NOK 1# Failed test (t/01load.t at line 7) > > # Tried to use 'DateTime::TimeZone'. > > # Error: Can't locate DateTime/TimeZoneCatalog.pm in @INC > > > > Did you forget to add this file to the CVS repository??? > > Oops, um, you need to run the script tools/parse_olson to generate most > of the time zone stuff. Something like: > > PERL5LIB=/path/to/DateTime.pm/lib/ tools/parse_olson --dir=/path/to/olson/files/ > > But now I realize DateTime.pm require DateTime::TimeZone, which require > DateTime::TimeZoneCatalog, which is generated, which requires ... > > Bootstrapping problem! > > I should probably just check in the generated files and be done with it. > Anyone have any objections to that?
Nope. It's the way many projects with generated files work, including perl. Tim.
