On Mon, Feb 03, 2014 at 04:15:07PM -0800, Timothy Gu wrote: >... > > On Feb 3, 2014 3:39 PM, "Jan Larres" <j...@majutsushi.net> wrote: > > > > > > On 04/02/14 12:08, Antoine Beaupré wrote: > > > > If both packages are ABI-compatible, then ffmpeg can be designed as a > > > > drop-in replacement for libav and users will be free to choose. > > > > > > As far as I understand it the problem is that it is *not* a drop-in > > > replacement as far as the libraries are concerned, every package needs > > > to be recompiled depending on which library should be used. So you would > > > need two different packages for every program that uses the libraries if > > > you wanted to offer both in parallel. And I don't think Adrian (or > > > anyone else) is against ffmpeg as such, it's just that there should be > > > made a decision which one to use in order to avoid these issues. > > > > It's not as bad as you think. FFmpeg has a > --enable-libav-incompatible-abi configure option. Didn't test the > effectiveness of it though.
This makes some functions that have different signatures in libav and ffmpeg API-compatible with libav by switching them to the libav one. It does not change the sonames of the ffmpeg libraries. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org