Log message:
revbump after devel/protobuf update

Log message:
postgresql-postgis2: reset PKGREVISION after update

Log message:
databases/postgresql-postgis2: Update to 3.5.1

Upstream NEWS, less bugfixes and minor improvements.

PostGIS 3.5.1
2024/12/22

* Bug fixes *

- #5823, Build support for Pg18 (Paul Ramsey)

* Enhancements *

  - #5782, Improve robustness of min distance calculation (Sandro Santilli)
  - [topology] Speedup topology building when closing large rings with many
    holes (Björn Harrtell)
  - #5810, [tiger_geocoder] Update tiger geocoder to handle TIGER 2024 data \ 
(Regina Obe)

* Breaking Changes *

  - #5799, make ST_TileEnvelope clip envelopes to tile plane
           extent (Paul Ramsey)

Log message:
databases/postgresql-postgis2: Alow pg17

The README does not say, but the release announcement for 3.5.0 says
"best served with PostgreSQL 17 RC1".  While it's ridiculous for a
release to recommend using a non-release, it's a clue that 17 should
be ok.

Log message:
*: remove references to pgsql 12

Log message:
revbump for x265

Log message:
*: recursive bump for icu 76 shlib major version bump

Log message:
databases/postgresql-postgis2: Remove buildlink3.mk

Postgis having a bl3 file is:

  - unused: no package (even in wip) includes it

  - conceptually wrong: When a package has postgis support, it does so
    by linking the postgresql client libs, and then sending queries
    with spatial objects across that connection.  There is nothing to
    link against.  And, just like any other use of a database, the
    server might be on some other machine -- so depending programs are
    simply clients anyway.

In theory this will change nothing and break nothing...

Log message:
databases/postgresql-postgis2: Fix ABI_DEPENDS package name

Log message:
*: revbump for gdal