Quoting Soft Works (2022-02-09 07:19:23) > > Sure. Don't understand my reply as an objection I don't even know what > xvmc is (or was). I rather see the burden and effort that it takes > to retain all those compatibility paths and at the same time how it > is blocking innovation and progress. > Compatibility is important - without question, but doing it in a way > that libs from different versions can be combined, is a somewhat crazy > endeavor. I keep wondering who would be the developer whose dreams > this might fulfil.. > The discussion about that seems to have gotten stuck about whether > to merge libs together or not, or how, but I haven't followed in > detailed, so please excuse the question (which has probably been > covered before): > Why can't ffmpeg simply declare that starting from version X, it > will be a requirement that all libs are from the same version? > (of course after equalizing)
That is pretty offtopic in this thread =p That said, in my opinion - the extra flexibility is useful - the actual effort required to allow mismatching versions is overstated - the things this mainly affects are various private interfaces, which IMO are a mispattern and should not exist anyway -- Anton Khirnov _______________________________________________ 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".
