On Mon, 2010-08-30 at 02:24 +1000, Daniel Burr wrote: > On 30/08/10 02:10, Sebastian Dröge wrote: > > Yes, you need a newer gstreamer0.10-ffmpeg version, like the one from > > experimental, to have it working with 0.6. That's known and will be > > fixed once 0.6 lands in unstable, nothing to worry about... > > Yes, you are quite right. I thought that I had already checked for the > presence of gstreamer0.10-ffmpeg 0.10.11 in experimental but it looks > like it was there all along. > > What do you think of my suggestion to create separate libavcodec60 and > libavformat60 packages to prevent having to recompile everything that > relies on ffmpeg 0.5.2?
I don't care, ffmpeg simply doesn't provide a stable API/ABI and that's something for the ffmpeg maintainers to worry about, really. But AFAIK there's no real API/ABI change between 0.5 and 0.6, only some private API has changed (which breaks mplayer for example... because it uses private API) and the problem with gst-ffmpeg simply was a bug IIRC.
signature.asc
Description: This is a digitally signed message part
