libgig 4.0.0 qsampler 4.2.0 gigedit 1.0.0

James Cowgill jcowgill at debian.org
Wed Nov 30 13:24:50 UTC 2016


Hi,

On 26/11/16 15:17, Jaromír Mikeš wrote:
> Quoting upstream answer
> --------------
> However my original suggestion for changing /usr/include/libgig to
> /usr/include/libgig4 might still make sense. Since all applications linking
> against libgig are calling pkg-config, they would still compile to that new
> headers location without any changes to those app's source code or configure
> scripts. Do your Debian friends over there have any profound reasons against
> this naming scheme (with the lib's major number included)?

I have no profound reasons against it - it's just completely pointless
unless you change the library name as well (ie libgig.so -> libgig4.so).
Also, it's generally not a good idea to assume that _everyone_ is using
pkg-config.

> But just to make this clear: libgig is also one of the libraries which was and
> will change its API frequently becoming incompatible with previous versions.
> That's mainly because we decided that preserving backward compatibility for a
> long time would mean to much work overhead for us, with probably no relevant
> advantage for users in practice.

That's unfortunate, but since the library isn't used by many packages
it's probably not too bad.

James

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20161130/0fa6f4c9/attachment.sig>


More information about the pkg-multimedia-maintainers mailing list