Chris Josephes <[EMAIL PROTECTED]> writes: [...]
> 2. Include a "make install-data" target that will unzip the data, and then > install it in a standard location your module will search by default. > Would /usr/share/postal/us be a bad place? Is anyone else doing this? The problem is that you can't easily do this from perl -MCPAN -e shell. None of the objections I've seen so far have related to the size of the data. There have been many concerns about the freshness, but because of how rarely it's updated (every 10 years) and the lack of a standard way to get and process the data, I think that there isn't really a better alternative. There have been many concerns about having to re-distribute the data when the code changes, or the code when the data changes, but the data is in a seperate module with very little code (26 lines), so I don't really think that's a problem, either. If you have any objections about the size of the file, or any other objections that haven't been brough up already, let me know; otherwise I'll recommend to TJ that he upload the Geo::PostalCode::US module with the data. Thanks for all the feedback! -----ScottG.
