Apologies for the last e-mail with vague subject line. Another thought on pgRouting dependencies-- any plans for cgal to be dropped once GEOS 3.4 is readily available? It seems like it could be with Delaunay being on GEO 3.4dev, but I don’t know when the line gets moved for minimum GEOS version (obviously sometime after it’s no longer a dev version).
Best,
Steve
On 5/10/2013 9:53 AM, Stephen Mather wrote:
Apologies for the last e-mail with vague subject line. Another thought
on pgRouting dependencies-- any plans for cgal to be dropped once GEOS
3.4 is readily available? It seems like it could be with Delaunay being
on GEO 3.4dev, but I don't know when the line gets moved for minimum
GEOS version (obviously sometime after it's no longer a dev version).
Yes, that is the ultimate plan. We have a little chicken vs egg issue in that we need the new postgis functions so we can rewrite our code as you point out. We also have to be careful to not set the required postgis version too high too soon, because that will be a problem for the packagers where new releases lag behind.
We have another options:
1. I have code that I could contribute as an interim solution, but that seems like a lot of work.
2. we could provide both a CGAL (depreciated) and a postgis SQL only solution that would only work if you have GEOS 3.4 install.
So we will see how this evolves, given other work, release deadlines, pull requests, funding, etc.
Thanks,
-Steve W
That makes sense. It’s funny, cause I am currently pulling my hair out with the opposite issue-- the cmake minimum not matching what’s available on Ubuntu 12.04, so yes-- no extra headaches in the form of dependency h*ll should ever be lightly foisted upon the unaware… :).
Best,
Steve
···
On Fri, May 10, 2013 at 10:13 AM, Stephen Woodbridge <woodbri@swoodbridge.com> wrote:
On 5/10/2013 9:53 AM, Stephen Mather wrote:
Apologies for the last e-mail with vague subject line. Another thought
on pgRouting dependencies-- any plans for cgal to be dropped once GEOS
3.4 is readily available? It seems like it could be with Delaunay being
on GEO 3.4dev, but I don’t know when the line gets moved for minimum
GEOS version (obviously sometime after it’s no longer a dev version).
Yes, that is the ultimate plan. We have a little chicken vs egg issue in that we need the new postgis functions so we can rewrite our code as you point out. We also have to be careful to not set the required postgis version too high too soon, because that will be a problem for the packagers where new releases lag behind.
We have another options:
-
I have code that I could contribute as an interim solution, but that seems like a lot of work.
-
we could provide both a CGAL (depreciated) and a postgis SQL only solution that would only work if you have GEOS 3.4 install.
So we will see how this evolves, given other work, release deadlines, pull requests, funding, etc.
Thanks,
-Steve W
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
On 5/10/2013 11:04 AM, Stephen Mather wrote:
That makes sense. It's funny, cause I am currently pulling my hair out
with the opposite issue-- the cmake minimum not matching what's
available on Ubuntu 12.04, so yes-- no extra headaches in the form of
dependency h*ll should ever be lightly foisted upon the unaware... :).
I just download the cmake source cmake-2.8.10.2.tar.gz and built that on debian. I know that is not desirable. Looks like you can get it from a PPA here:
http://www.ubuntuupdates.org/package/kubuntu-ppa_backports/precise/main/base/cmake
-Steve
Best,
Steve
On Fri, May 10, 2013 at 10:13 AM, Stephen Woodbridge
<woodbri@swoodbridge.com <mailto:woodbri@swoodbridge.com>> wrote:
On 5/10/2013 9:53 AM, Stephen Mather wrote:
Apologies for the last e-mail with vague subject line. Another
thought
on pgRouting dependencies-- any plans for cgal to be dropped
once GEOS
3.4 is readily available? It seems like it could be with
Delaunay being
on GEO 3.4dev, but I don't know when the line gets moved for minimum
GEOS version (obviously sometime after it's no longer a dev
version).
Yes, that is the ultimate plan. We have a little chicken vs egg
issue in that we need the new postgis functions so we can rewrite
our code as you point out. We also have to be careful to not set the
required postgis version too high too soon, because that will be a
problem for the packagers where new releases lag behind.
We have another options:
1. I have code that I could contribute as an interim solution, but
that seems like a lot of work.
2. we could provide both a CGAL (depreciated) and a postgis SQL only
solution that would only work if you have GEOS 3.4 install.
So we will see how this evolves, given other work, release
deadlines, pull requests, funding, etc.
Thanks,
-Steve W
_________________________________________________
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org <mailto:pgrouting-dev@lists.osgeo.org>
http://lists.osgeo.org/__mailman/listinfo/pgrouting-dev
<http://lists.osgeo.org/mailman/listinfo/pgrouting-dev>
_______________________________________________
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
Cool. Tried jerry-rigging it first with changing the dependency declaration, but that’s a real dependency it seems.
Ya, cmake isn’t too bad to build, so done.
Best,
Steve
···
On Fri, May 10, 2013 at 11:24 AM, Stephen Woodbridge <woodbri@swoodbridge.com> wrote:
On 5/10/2013 11:04 AM, Stephen Mather wrote:
That makes sense. It’s funny, cause I am currently pulling my hair out
with the opposite issue-- the cmake minimum not matching what’s
available on Ubuntu 12.04, so yes-- no extra headaches in the form of
dependency h*ll should ever be lightly foisted upon the unaware… :).
I just download the cmake source cmake-2.8.10.2.tar.gz and built that on debian. I know that is not desirable. Looks like you can get it from a PPA here:
http://www.ubuntuupdates.org/package/kubuntu-ppa_backports/precise/main/base/cmake
-Steve
Best,
Steve
On Fri, May 10, 2013 at 10:13 AM, Stephen Woodbridge
<woodbri@swoodbridge.com mailto:[woodbri@swoodbridge.com](mailto:woodbri@swoodbridge.com)> wrote:
On 5/10/2013 9:53 AM, Stephen Mather wrote:
Apologies for the last e-mail with vague subject line. Another
thought
on pgRouting dependencies-- any plans for cgal to be dropped
once GEOS
3.4 is readily available? It seems like it could be with
Delaunay being
on GEO 3.4dev, but I don’t know when the line gets moved for minimum
GEOS version (obviously sometime after it’s no longer a dev
version).
Yes, that is the ultimate plan. We have a little chicken vs egg
issue in that we need the new postgis functions so we can rewrite
our code as you point out. We also have to be careful to not set the
required postgis version too high too soon, because that will be a
problem for the packagers where new releases lag behind.
We have another options:
-
I have code that I could contribute as an interim solution, but
that seems like a lot of work.
-
we could provide both a CGAL (depreciated) and a postgis SQL only
solution that would only work if you have GEOS 3.4 install.
So we will see how this evolves, given other work, release
deadlines, pull requests, funding, etc.
Thanks,
-Steve W
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org mailto:[pgrouting-dev@lists.osgeo.org](mailto:pgrouting-dev@lists.osgeo.org)
http://lists.osgeo.org/__mailman/listinfo/pgrouting-dev
<http://lists.osgeo.org/mailman/listinfo/pgrouting-dev>
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
pgrouting-dev mailing list
pgrouting-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/pgrouting-dev