#38353 closed defect (wontfix)
pgRouting: fetch error
Reported by: | manalorama@… | Owned by: | Veence (Vincent) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.1.3 |
Keywords: | Cc: | ||
Port: | pgRouting |
Description (last modified by larryv (Lawrence Velázquez))
Hello,
Can you please check if you can make it available, or should install it using a different method? I have tried to download the source pgrouting-1.05.tar.gz from http://pgrouting.org/download.html and compile, but it doesn't contain the configure file,
First time I tried, it resolved all dependencies and downloaded, but then produced the following output and every time I try again:
$sudo port install pgrouting Password: ---> Computing dependencies for pgRouting ---> Fetching distfiles for pgRouting Error: pgRouting is currently out of date, buggy and broken. Error: org.macports.fetch for port pgRouting returned: Port disabled Please see the log file for port pgRouting for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_gis_pgRouting/pgRouting/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port pgrouting failed
thank you very much,
Change History (9)
comment:1 Changed 12 years ago by larryv (Lawrence Velázquez)
Description: | modified (diff) |
---|---|
Owner: | changed from macports-tickets@… to vince@… |
Port: | pgRouting added |
Summary: | pgRouting is currently out of date, buggy and broken. → pgRouting: fetch error |
comment:2 Changed 12 years ago by Veence (Vincent)
Resolution: | → wontfix |
---|---|
Status: | new → closed |
There is absolutely nothing I can do. PgRouting as such is dead: last release dates back to October 2011. This 1.05 version is incompatible with PostgreSQL 9, requires an antiquated Boost version and is moreover buggy. The only sensible thing to do would be to remove the port from the list.
There is, however, a faint probability for pgRouting code/functionality to be integrated in a future release of PostGIS. But this is a mere rumor, and no milestone has been set.
Sorry…
comment:4 Changed 12 years ago by larryv (Lawrence Velázquez)
It’s been 11 months and several Postgres and Boost updates since r91463, so deleting it altogether would probably be fine. It’s up to you, really. :P
comment:5 Changed 12 years ago by jmroot (Joshua Root)
If the port is never going to work again, then yes, you should delete it.
comment:6 follow-up: 7 Changed 12 years ago by jmroot (Joshua Root)
However, it looks like upstream development is not dead after all? There were two GSoC projects in 2012, and there is talk on the mailing list this month of a 2.0 release being developed.
comment:7 Changed 12 years ago by cooljeanius (Eric Gallager)
Replying to jmr@…:
However, it looks like upstream development is not dead after all? There were two GSoC projects in 2012, and there is talk on the mailing list this month of a 2.0 release being developed.
Good, I'm hoping this doesn't have to get deleted
comment:8 Changed 12 years ago by Veence (Vincent)
Well, I will ask the mailing list about this hypothetical 2.0 version and act accordingly.
comment:9 Changed 12 years ago by Veence (Vincent)
Okay. If I believe the wiki page for the ‘2.0’ version, the future release is still months away at best. It is not even sure that pgRouting will reappear as a separate package, but rather as a postGIS extension, in which case it would become a variant of the PostGIS 2 port. I am going to remove the port in order to avoid luring people into believing the port exists and works, and as soon as something is out, I will either recreate one or add a variant to PostGIS 2.
pgRouting was intentionally disabled in r91463.