Comment 6 for bug 1525156

Right, I know they don't interact in a code sense. I meant the deprecation aspect.

You mention not hitting the network and I see by looking at the geonames code that it bundles cities15000.txt into itself to avoid hitting the network.

libtimezonemap also ships cities15000.txt on disk to work offline... (although, bizarrely the timezone completion part of it doesn't use it? -- maybe we could have fixed that and added some API instead of making a new library?)

But anyway, that's the sort of 5M duplication I'm trying to avoid and why I asked about their interaction. For example, geonames could have simply depended on libtimezonemap-data and not wasted 5M of space.

It's also annoying that geonames doesn't use a separate geonames-data package for that content. Avoids wasted space during SONAME transitions and makes the file available for others to parse in case they want to. For example, you could have shipped it on disk and then had libtimezonemap depend on it and drop its own data files.