2019-04-10 2:40 GMT+02:00, Baptiste Coudurier <baptiste.coudur...@gmail.com>: > >> On Apr 9, 2019, at 5:24 PM, James Almer <jamr...@gmail.com> wrote:
>> More than one ffmpeg release will ship with libavcodec/libavformat >> sharing the same soname. Backwards compatibility is expected, hence the >> split between major, minor and micro, as you're meant to be able to drop >> a newer libavcodec library, say for example ffmpeg 4.1's >> libavcodec.58.so, and it should work with an existing libavformat.so.58 >> that was linked against ffmpeg 4.0's libavcodec.58.so. > > Sorry to repeat the question but when did that change ? > Which practical use case are we covering here ? > You were never supposed to update libavcodec without > updating libavformat If you use libavformat in the first place. While we have violated this before, we of course claim compatibility, so this argument is not helpful, sorry. Carl Eugen _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".