Bug#712688: transition: gdal
I'm going to provide a long due change to gdal library (current 1.9.0) in sid.
In order to solve properly problems of programs that both link geotiff, tiff
and gdal libraries, I'm going to drop direct tiff/geotiff functions providing.
Upstreams provide now a renaming feature for that (note that the internal
gdal version indeed use a bit different ABI) and the result will be a
bit different API/ABI starting from next 1.10.0 version.
(See http://wiki.orfeo-toolbox.org/index.php/Link_conflicts about that and
the partially working fix of #558733)
Unfortunately, upstreams do not consider that a true API change (in some way the
use of geotiff/tiff funcs out of the gdal interface is considered de facto
a deprecated use). So the official upstream soname is indeed the same.
BTW, without annoying all of you with a so looooooong history about
this issue, I'm going to introduce a new libgdal1h binary package (h means hidden, better
suggestions are welcome :)), with a new SONAME libgdal.1h to manage a decent migration
to the new flavor. This will sacrifice third-parties sw compatibility, but
well, who cares? It would be break anyway.
That could also imply that some r-deps will have to explicitly link now
tiff/geotiff libraries instead of using the gdal inner one.
As usual I will start all the transition in experimental ASAP.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.9-1-686-pae (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash