On Thu, 6 Jan 2005, Scott W Gifford wrote: > If the user has custom data, they would just install Geo::PostalCode > and build their own database (it includes a short script to do this, > and the process takes about 2 minutes). Geo::PostalCode::US doesn't > replace Geo::PostalCode, but just adds a second module with the data.
I think the thing that is still gnawing at me is having one perl module that is just data. Other guys do it, but the data in Geo::Postal is actually really, really useful. What about this option? 1. Include the datafiles, either compressed or uncompressed with the module distribution. 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? 3. Whenever the Geo::Postal code is updated, include the latest datafiles. 4. If the datafiles get updated, and it does not coincide with a code release, make sure people know where to get those files (either point them to the Cencus website, or provide your own zipfile distro). That way you bundle the data with the code, and you give end-users the option of whether or not they want to use the data you provide. -------------------- Christopher Josephes [EMAIL PROTECTED]
