Changes in GEOS library
- To: basemap@packages.debian.org, python-shapely@packages.debian.org, player@packages.debian.org, spatialite-gui@packages.debian.org, gdal@packages.debian.org, spatialite@packages.debian.org, qgis@packages.debian.org, mapserver@packages.debian.org, osgearth@packages.debian.org, postgis@packages.debian.org, osmium@packages.debian.org, mapnik@packages.debian.org, osm2pgsql@packages.debian.org
- Cc: debian-release@lists.debian.org
- Subject: Changes in GEOS library
- From: "Francesco P. Lovergine" <frankie@debian.org>
- Date: Wed, 22 Feb 2012 13:36:46 +0100
- Message-id: <[🔎] 20120222123646.GC2529@blegrez.ba.issia.cnr.it>
Dear maintainer
you are receiving this mail as a mantainer of one or more packages related
to the `geos' library (i.e. having libgeos-dev as a build-dep).
With next 3.3.1+ version, I'm going to split appropriately the Geos C and C++
interfaces as explained in #643658.
Most programs require tipically linking the official stable C interface,
so libgeos-dev from now on will provide *only* the libgeos_c dev stuff and
headers. You will need to build-dep on the libgeos++-dev package if
your program *explicitly* use the C++ interface, instead.
That will allow me to avoid calling at every new geos release
a bin-NMU batch run for ALL r-builddeps, because in the 90% of cases
new releases hide in the unstable C++ library all details of
changes. Your program in most cases simply does
not use the OO interface, as shown in
http://trac.osgeo.org/geos/wiki/Applications
For instance, osm2pgsql is expected to FTBS and should be the
only package strictly depending on the C++ interface, ATM.
PS:
CCing release team for information about next changes.
--
Francesco P. Lovergine
Reply to: