On 08/12/2014 11:26 AM, Emilio Pozuelo Monfort wrote: > On 02/08/14 20:41, Bas Couwenberg wrote: >> Updating GDAL from 1.10.1 to 1.11.0 involves a SONAME bump from >> libgdal.so.1.17.1 to libgdal.so.1.18.0. >> >> Because the binary package name doesn't change, I don't know how to >> format a Ben file to track this. > > Err. What? Are you bumping the SONAME without renaming the package? Why? Why > isn't the package named after the SONAME as it should be? What am I missing?
Sorry about creating such confusion by badly wording the issue. The SONAME doesn't change, it remains at libgdal.so.1, only the library version changes. The package is named libgdal1h to differentiate it from its predecessor libgdal1 after the reintroduction of internal symbols hiding for better compatibility against mixing external geotiff and gdal. Because the libgdal exposes both C and C++ symbols, its reverse dependencies need a rebuild to make sure they continue to work in case they don't only use the stable C API but also the unstable C++ API. Does it make sense to you now? > Emilio Kind Regards, Bas -- GPG Key ID: 4096R/E88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53e9e165.3050...@xs4all.nl
