No subject


Thu Feb 21 13:22:13 CET 2013


ote">From what I recall, the 0.6 version was the first=C2=A0 release to hav=
e a completely different soname than the latest ffmpeg at the date it was i=
ntroduced. So it was possible to install theses compat libraries along with=
 a modern ffmpeg (provided that no project was resolving symbol at runtime,=
 or using dependencies linked with both ffmpeg library version).<br>
<br></div><div class=3D"gmail_quote">One other reason to choose 0.6 instead=
 of 0.7 at that time was that many of the improvements of 0.7 over 0.6 was =
related to make it easier for project using ffmpeg to be compatible with mo=
re modern API. It was also related to the split between FFmpeg/Libav becaus=
e FFmpeg try to keep compatibility. And just after the split, the early 0.7=
 branch was not as good as using release before the split IMO.<br>
</div><div class=3D"gmail_quote">Compatibility API is not something targete=
d for such compat package, as the aim is to stay with a given API. So=C2=A0=
 the 0.6 version was picked instead.<br><br></div><div class=3D"gmail_quote=
">So if it&#39;s easier to maintain 0.5, it can be downgraded to that versi=
on instead and rebuild the dependencies.<br>
</div><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">Nicol=
as (kwizart)<br></div><div class=3D"gmail_quote"><br></div><br><div class=
=3D"gmail_quote"><br><br><br></div></div></div>

--001a113330209f46ff04dd9cbcd8--


More information about the rpmfusion-developers mailing list