On Mon, Sep 5, 2011 at 10:46 AM, Francesco P. Lovergine
<fran...@debian.org> wrote:

> Yep, I will introduce versioning in the incoming 1.8 series to solve
> this problem. Unfortunately this will also break binary compatibility
> with third-parties programs not built against Debian Gdal. So I will
> also expect a few complains about that... :-/

I understand that -merely by the number and importance of packages
affected- the libtiff transition is not going to happen soon.
But I still wonder what's blocking the release of libtiff 4.0 (and
libtiff5 for unstable). Or to put things differently: why do we (and
the gdal maintainers) consider libtiff5 stable enough for gdal, if it
is not yet released*? We could also choose to use the system version
and live without bigtiff support, it's a different way of solving this

*: Upstream bugs for libtiff:

Pkg-grass-devel mailing list

Reply via email to