cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
138,953 Commits 1 Branch 0 Tags
Commit Graph

26 Commits

Author SHA1 Message Date
landry
2b03531bed Update to pgrouting 2.6.1 2018-09-30 11:46:43 +00:00
landry
4742a6ee98 Actually switch to 'real' uploaded tarballs and not git-autogenerated 
ones, thanks to upstream. Checksum/size doesnt change so no need to
append the _1 suffix.

Cf https://github.com/pgRouting/pgrouting/issues/1013
 2018-04-05 15:05:21 +00:00
landry
8f3b735339 Remove now useless patch that doesnt apply anymore, reported by naddy@ 2018-04-02 20:05:23 +00:00
landry
c662b60258 Update to pgrouting 2.6.0. 
Switch to real releases hosted on github while here.
 2018-04-01 18:44:59 +00:00
jeremy
666843dfad Add patch to work with PostgreSQL 10. 
OK pea@
 2017-11-30 16:23:07 +00:00
landry
5ea63ea67e Update to pgrouting 2.5.2. 
Use a variable like in postgis to avoid big PLIST churn at each update.
 2017-11-21 20:41:18 +00:00
naddy
11e3dd67b3 switch COMPILER from the old, confusing shortcuts to the more explicit format 2017-11-16 23:20:37 +00:00
landry
00fb46f4b8 Update pgrouting to 2.5.1. 2017-10-28 17:37:30 +00:00
landry
1ee934eb1e Update to pgrouting 2.5.0. 
See
https://github.com/pgRouting/pgrouting/wiki/Migration-Guide#migrating-from-24-to-25
for details.
 2017-09-18 08:23:36 +00:00
landry
77019798cb Update to pgrouting 2.4.2. 2017-08-28 10:03:19 +00:00
sthen
5e964ab0df bump LIBCXX/LIBECXX/COMPILER_LIBCXX ports. 2017-07-26 22:45:14 +00:00
espie
8ac47fd9c6 use COMPILER_LIBCXX where applicable 2017-07-16 19:18:47 +00:00
espie
cc5bc426ed switch everything to new COMPILER idiom, even stuff that won't build with clang 
yet, but at least that part is done.
 2017-05-31 08:08:15 +00:00
espie
6d4b1804b4 WANT_CXX 2017-05-27 04:54:31 +00:00
landry
42913f3bf3 Update to pgrouting 2.4.1. 2017-04-28 10:42:42 +00:00
landry
5b7a21f817 Update to pgrouting 2.3.0. 
http://docs.pgrouting.org/2.3/en/doc/src/changelog/release_notes.html#changelog-2-3-0
 2016-10-31 17:59:01 +00:00
sthen
1d81a7f192 sync WANTLIB 2016-07-09 09:09:08 +00:00
naddy
42bc647e80 remove SHARED_ONLY from ports that only use modules that neither set nor 
read this variable
 2016-03-18 23:12:15 +00:00
landry
7470b9215b Update to pgrouting 2.1.0. 
Tested with grenoble data from mapzen metro extracts, imported with
osm2pgrouting, and using pgRoutingLayer extension in QGIS.
 2015-09-19 15:44:12 +00:00
sthen
7d3936afa9 sync WANTLIB 2015-08-21 22:51:09 +00:00
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