cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Import pgrouting 2.0.0

Browse Source 
pgRouting extends the PostGIS / PostgreSQL geospatial database to provide
geospatial routing functionality.

Advantages of the database routing approach are:

* Data and attributes can be modified by many clients, like QGIS and
  uDig through JDBC, ODBC, or directly using Pl/pgSQL. The clients can
  either be PCs or mobile devices.
* Data changes can be reflected instantaneously through the routing
  engine. There is no need for precalculation.
* The "cost" parameter can be dynamically calculated through SQL and its
  value can come from multiple fields or tables.

ok sthen@
This commit is contained in:
landry 2014-12-16 21:34:35 +00:00
parent 3c28eb1c6c
commit 6f94030683
4 changed files with 60 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
geo/pgrouting/Makefile Normal file
View File

@ -0,0 +1,30 @@
# $OpenBSD: Makefile,v 1.1.1.1 2014/12/16 21:34:35 landry Exp $
SHARED_ONLY = Yes
COMMENT = geospatial routing extension for PostgreSQL
GH_TAG = v2.0.0
GH_COMMIT = d6ed2cba4c574b8ac463632df451b6f011fd522d
GH_PROJECT = pgrouting
GH_ACCOUNT = pgRouting
DISTNAME = pgrouting-2.0.0
CATEGORIES = geo databases
HOMEPAGE = http://pgrouting.org/
MAINTAINER = Landry Breuil <landry@openbsd.org>
# GPLv2
PERMIT_PACKAGE_CDROM= Yes
MODULES = devel/cmake
LIB_DEPENDS = math/cgal
RUN_DEPENDS = databases/postgresql,-server
BUILD_DEPENDS = databases/postgresql,-server
WANTLIB += CGAL boost_system-mt boost_thread-mt gmp m stdc++
NO_TEST = Yes
.include <bsd.port.mk>

2
geo/pgrouting/distinfo Normal file
View File

@ -0,0 +1,2 @@
SHA256 (pgrouting-2.0.0.tar.gz) = g96NhWAvpojJaYTD16itpb92+MSr/DNXjhZzyZ+jz3g=
SIZE (pgrouting-2.0.0.tar.gz) = 3766086

12
geo/pgrouting/pkg/DESCR Normal file
View File

@ -0,0 +1,12 @@
pgRouting extends the PostGIS / PostgreSQL geospatial database to provide
geospatial routing functionality.
Advantages of the database routing approach are:
* Data and attributes can be modified by many clients, like QGIS and
uDig through JDBC, ODBC, or directly using Pl/pgSQL. The clients can
either be PCs or mobile devices.
* Data changes can be reflected instantaneously through the routing
engine. There is no need for precalculation.
* The "cost" parameter can be dynamically calculated through SQL and its
value can come from multiple fields or tables.

16
geo/pgrouting/pkg/PLIST Normal file
View File

@ -0,0 +1,16 @@
@comment $OpenBSD: PLIST,v 1.1.1.1 2014/12/16 21:34:35 landry Exp $
lib/postgresql/librouting.so
lib/postgresql/librouting_bd.so
lib/postgresql/librouting_dd.so
lib/postgresql/librouting_ksp.so
lib/postgresql/librouting_tsp.so
share/postgresql/contrib/
share/postgresql/contrib/pgrouting-2.0/
share/postgresql/contrib/pgrouting-2.0/pgrouting.control
share/postgresql/contrib/pgrouting-2.0/pgrouting.sql
share/postgresql/contrib/pgrouting-2.0/pgrouting_dd_legacy.sql
share/postgresql/contrib/pgrouting-2.0/pgrouting_legacy.sql
share/postgresql/extension/pgrouting--2.0.0.sql
share/postgresql/extension/pgrouting.control
share/postgresql/extension/pgrouting_dd_legacy.sql
share/postgresql/extension/pgrouting_legacy.sql