Bug#879673: ffmpeg 3.4 API compat layer not 100% backwards compatible

[Sebastian Dröge]

On Tue, 2017-10-24 at 13:44 +0100, James Cowgill wrote:
> > gst-libav upstream bug can be found here:
> > https://bugzilla.gnome.org/show_bug.cgi?id=789193
> 
> OK, hopefully upstream ffmpeg can help fixing this bug, since I'm not
> sure what I can do about it.

It seems like it also introduces severe performance regressions as
zerocopy decoding is not possible anymore with the compatibility layer.

> > We'll try to port over to the new API but it looks like some
> > effort,
> > and even independent of that the compatibility layer should either
> > be
> > fixed or the soname of the libraries has to be updated.
> 
> Updating SONAMEs doesn't help when there's an API break and the
> behavior of existing functions has changed.

It's simply the right thing to do if you break the API/ABI. That's why
the soname exists to begin with :)

Also it makes sure that all software is actually ready for the new
version as it requires rebuilding/relinking to the new name, and
generally makes it far more explicit that there was breakage and stuff
has to be updated.


All that of course only if the ffmpeg people don't consider this a bug
in the compatibility layer but instead an intentional breakage.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20171024/d43d8f08/attachment.sig>