Re: Upcoming libgd2-{xpm,noxpm}-dev -> libgd2-dev transition

[Guillem Jover <guillem@debian.org>]

Hi!

On Mon, 2013-05-13 at 22:34:36 +0200, Ondřej Surý wrote:
> Two things has happened with GD Library:
> 
> 1. I have dropped the {xpm,noxpm} dichotomy and there's only
>    libgd2-dev now.  There are transitional packages which are ment
>    to help with the move to libgd2-dev, so you don't have to make
>    any changes right now - the binNMUs should work.

Might I suggest libgd-dev instead? If a later API revision makes lots
of other packages FTBFS, a new versioned libgdN-dev package can always
be introduced; otherwise unversioned ones in case of say just ABI bumps
are more correct and cause less painful transitions.

> 2. The upstream, which I accidentaly became part of, has released
>    libgd-2.1.0-alpha1 today.  This release has merged most of the code
>    from PHP fork of the library (only some custom antialiasing stuff
>    was not merged).  But beware not, the API was kept backwards
>    compatible.
> 
>    The ABI has remained same as well, but I have decided to bump the
>    SONAME to 3, because I have implemented the GCC visibility magick,
>    so only symbols, which were ment to be exposed, are exposed now.

If the SOVERSION is now 3, then the shared library package would need
to be called libgd3 (and libgd3-dev or as mentioned above ideally
libgd-dev), or did I misunderstood something in the above?

Thanks,
Guillem