CSV support would be key to be able to use this in conjunction with geolite2legacy

[rcfa]

CSV support would be key to be able to use this in conjunction with https://github.com/sherpya/geolite2legacy to keep some legacy software operating, in particular scripts using geoiplookup, which depends on the legacy format database.

The debian geoipupdate package keeps the /var/lib/GeoIP/ up to date, but /var/share/GeoIP obviously not. All that's needed is a cron script running geolite2legacy. But that requires that geoipupdate can handle CSV files.

[oschwald]

I don't know that we are likely to add CSV support to this tool. The MMDB files are generally used directly and can easily be updated atomically.

With the CSVs, they are generally ingested as part of a pipeline and they are generally just an intermediate format that does not need to persist on disk. In most cases, it makes more sense to download the files as needed as part of the build process. Also, since most of the CSV databases consist of multiple files, it is difficult to have any guarantees around the updates being atomic.