all: Bump PORTREVISION after lang/go{119,120} update

databases/pg_tileserv: fix build on riscv64

Bump golang.org/x/sys dependency to a version new enough
to support riscv64-freebsd.

Sponsored by:	Berliner Linux User Group e.V.
Approved by:	portmgr (build fix blanket)
Differential Revision: https://reviews.freebsd.org/D39163

all: Bump PORTREVISION after Go ports update

all: Bump PORTREVISION after lang/go{119,120} update

all: Bump PORTREVISION after GO_DEFAULT update.

all: Bump PORTVERSION after lang/go{118,119} update

all: Bump PORTREVISION after lang/go{118,119} update

all: Bump PORTREVISION after lang/go{118,119} update

databases/pg_tileserv: Update to 1.0.9

all: Bump PORTREVISION after lang/go{118,119} update

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

all: Bump PORTREVISION after Go update

Bump Go ports PORTREVISION after GO_DEFAULT and lang/go118 update.

all: Bump PORTREVISION after lang/go{117,118} update

*/*: Bump port revisons after lang/go{117,118} update

*/*: Bump PORTREVISION after lang/go 1.18 update

databases/pg_tilserv: add new port

pg_tileserv is a PostGIS-only tile server written in Go.
By restricting itself to only using PostGIS as a data source,
pg_tileserv gains the following features:

- Automatic configuration. The server can discover and
automatically publish as tiles sources all tables it has read
access to: just point it at a PostgreSQL/PostGIS database.

- Full SQL flexibility. Using function layers, the server can
run any SQL to generate tile outputs. Any data processing,
feature filtering, or record aggregation that can be expressed in SQL,
can be exposed as parameterized tile sources.

- Database security model. You can restrict access to tables and
functions using standard database access control.
This means you can also use advanced access control techniques,
like row-level security to dynamically filter access based on the
login role.

WWW: https://github.com/crunchydata/pg_tileserv/issues