PostGIS adds support for geographic objects to the PostgreSQL
object-relational database. In effect, PostGIS "spatially enables"
the PostgreSQL server, allowing it to be used as a backend spatial
database for geographic information systems (GIS), much like ESRI's
SDE or Oracle's Spatial extension. PostGIS follows the OpenGIS
"Simple Features Specification for SQL" and has been certified as
compliant with the "Types and Functions" profile.
PostGIS development was started by Refractions Research as a project
in open source spatial database technology. PostGIS is released
under the GNU General Public License. PostGIS continues to be
developed by a group of contributors led by a Project Steering
Committee and new features continue to be added.
===> The following configuration options are available for postgis36-3.6.4_1:
ADDRSTD=on: Enable address standardizer
JSON=on: Enable JSON support
LOADERGUI=on: Enable shp2pgsql-gui
NLS=on: Enable international language support
PROTOBUF=on: Enable protocol buffers
RASTER=on: Enable raster support
SFCGAL=on: Enable sfcgal
TOPOLOGY=on: Topology support
===> Use 'make config' to modify these settings
Reason:
databases/postgis36 was missing PKGNAMESUFFIX and therefore built a
package named postgis rather than postgis36, unlike every other PostGIS
port. Because that unsuffixed name does not match the
CONFLICTS_INSTALL=postgis[0-9][0-9] declared by postgis33, postgis34,
postgis35 and postgis37, those ports did not register a conflict with
it, and an incompatible pair was only caught late, as a file conflict
at install time.
The package is now named postgis36. The origin is unchanged, so rename
the installed package before upgrading:
# pkg set -n postgis:postgis36
# pkg upgrade
Users of the other PostGIS ports need to do nothing.
*/*: De-orbit alias.mk
Mk/Uses/alias.mk was an attempt for compat with DPorts, but has rotted.
This feature was never documented in the PHB, so there is no work to
be done by the docs@ team.
Nothing against DragonFly, but if DPorts still needs FreeBSD 9
support, they really should work that out with upstream projects.
Ultimately, we don't need to keep carrying this outdated feature that
doesn't affect us.
