libgig 4.0.0 qsampler 4.2.0 gigedit 1.0.0

Jaromír Mikeš mira.mikes at gmail.com
Wed Nov 30 15:38:10 UTC 2016


Hi,

2016-11-30 14:24 GMT+01:00 James Cowgill <jcowgill at debian.org>:
> 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.

thank you James for comments ... can you please review libgig now if
it is ready for uploading to experimental?

best regards

mira



More information about the pkg-multimedia-maintainers mailing list