On 13/04/2024 14:09, Brian Inglis via Cygwin-apps wrote:
I would like to adopt and revive the above packages with the last
("unofficial") version of the legacy code committed noted in the
ChangeLog as 1.7.0, and a new upstream source for legacy format free
databases converted when the official current upstream databases are
updated.
My very limited, vague understanding was that GeoIP is obsolete and
users should move to something newer? What packages do we have that
actually depend on this? Are there other ways to update them?
Is there any easy way of overridding package version from
ac_init_version without patching configure.ac?
Generally, no.
As part of this upgrade, the geoipupdate source and databases are no
longer available, so the new upstream database source update script
becomes a new database subpackage and script geoipupdate, and the old
geoipupdate source, binary, and debuginfo packages should become obsolete.
Is there anything special required to replace a source package and
binaries with a binary subpackage?
Uh... I had to reread that several times (and compare with the cygport)
before it this question made sense.
So: when you come to upload, I'll need to change things to that the
geoipupdate package belongs to GeoIP-database source.
geoipupdate should probably obsolete geoipupdate-debuginfo, if it's now
empty.
Reviewing the cygports, everything looks OK.
I'd make the comment that the text about scheduling geoipupdate to run
should be in geoipupdate_DESCRIPTION, rather than in GeopIP-database's
description.
I added GeoIP and GeoIP-database to your packages.
