6 Commits

Author SHA1 Message Date
sthen
920bb14462 this was GH_TAG not GH_TAGNAME so got caught by poisoning. comment-out for now,
rather than regenning distinfo.
2015-04-05 14:58:42 +00:00
sthen
f12e6be118 drop GH_COMMIT lines which are hidden behind GH_TAGNAME,
discussed with a few in the room.
2015-04-05 13:31:13 +00:00
sthen
7734005f4d repair hand-edited patch (hint: use "editdiff" from patchutils) 2015-01-14 10:58:44 +00:00
zhuk
e938ade264 Use new shiny postgresql.port.mk.
Input for pgrouting part and okay for it from landry@
2015-01-12 20:57:55 +00:00
landry
b281b80dc3 Enable the regress test like its done for postgis (prompted by zhuk@,
thanks!) - fix RDEP while here, postgis is needed at runtime.
2014-12-19 21:16:55 +00:00
landry
6f94030683 Import pgrouting 2.0.0
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@
2014-12-16 21:34:35 +00:00