On 11.08.2015 11:34, Anton Khirnov wrote: > This API is dangerous -- it manipulates AVFrame internals from > libavcodec, even though AVFrame now lives in libavutil. It can break > badly if AVFrame is extended in libavutil, but libavcodec is not > updated. I think it also leaks side data, which cannot be fixed while > preserving compatibility. > > So I really do not think keeping it is a good idea, especially since > fixing this specific change should be very easy in most cases.
On the other hand, breaking many API users isn't good either. However, endlessly arguing which of these is the lesser evil isn't getting us anywhere. The best way forward is to get API users fixed. Thus I'll try to fix all affected packages in Debian, but I don't know how much time that will take. I suggest that we table the discussion until sometime closer to the release, maybe in a month? If most packages are fixed by then, this API could be removed, otherwise it might be better to delay it's removal (or the release). Best regards, Andreas _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
