When I made recent changes to my tzdata package, I included a module that automates the process of re-building the package. (It downloads the latest version of the tz data and its associated code, builds the zoneinfo database from it, and constructs an info.rkt file for it.) I have a similar kind of script in the works for my next version of the CLDR packages.
Is there any kind of convention about where this kind of code should go? For obvious reasons, I want it to be in the same repository as the package itself, but it really doesn't need to be distributed as part of the package. I could put it in its own <pkg name>-build directory from the repo root, just like I might have -lib, -doc, and -test packages. (The -test packages aren't terribly interesting from a distribution standpoint either.) I'm just curious if anyone else has thought about this or has any good ideas. - Jon -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
