Am 06.12.2013 15:08, schrieb Tomáš Chvátal:
Dne Pá 6. prosince 2013 13:48:12, Cristian Morales Vega napsal(a):
What's your plan? Understanding now that we are distributing ffmpeg anyway (inside Chromium, AFAIS is not libav) I am all for distributing it in a proper way.
Exactly we distribute it anyway. :)
My plan for now is frozen in legal queue still. So after that happens
Some questions: a) There is any officially stated policy about security maintenance in either libav or ffmpeg? I see ffmpeg 0.5.13 was released on 2013-09-25, while 0.5 was released on 2009-03-02. So I am not soooo worried about this, but still it doesn't seem to be anything clearly stated.
I spoke with libav lads and they plan to support each branch for quite few years which is over our attention span. Also I can get them to provide the statement on web.
I picked libav because nowdays they are more conservative in the features and
You mean: no new features for the last few years. I personally hate that.
thus less updates are usually needed when the release the thing. And as I know few people from the team they were really helpfull in identification of what is patented and whatnot and provided me the switches needed, etc.
Also wrt support we can stick with the debian stuff here as if we match the versions we should be covered really well. Wether debian does it, or upstream does it and we can slack and play with other stuff :P
Fortunately, the "get ffmpeg back into debian" movement is getting stronger, so even debian might have a proper package, soon ;-)
b) How is the compatibility between libav and ffmpeg? It's quite clear that the 0.5 series were compatible. I didn't look into it but it seems that as independent projects they have been correctly increasing the soname number whenever they did an incompatible change. But are they still using the same library names? Is the libavcodec/avformat/avutl/etc from libav 9.10 compatible with the versions from ffmpeg X (X being the branch using the same soname number)?
Quite-ish compatible I would say. 99% of the stuff is compatible.
Well, but only if the software is older than a few years. All the cool new useful features are in ffmpeg, none of them are in libavcodec. And stuff like libavfilter and swscale is very different IIRC (I'm not entirely sure what it was, but finally I decided to ditch the libav cr*p on my raspbian and compile a "real" ffmpeg to get anything useful done in my projects).
I am aware that the xbmc is not compatible with libav, but even tho there were some patches that enable the support they were not incorporated by upstream choice (I built it localy for testing purposes with it and it went fine tho, even my movie collection was played well).
Playing movies (e.g. just decoding common stuff) ist the least demanding stuff you can do with libav/ffmpeg. That's not a good benchmark.
The sonames are set by both project properly so if the soname is equal the pkgs should run.
One other issue might be with ffmpeg command, as libav provides different rewrote binary avconv. Provides +- equal functionality but the syntax is slightly different and I dunno if upstream plans to do something about it.
No, they deliberately changed stuff to be incompatible (also with the above mentioned filter/scale API differences), so I don't see them "fixing" it. -- Stefan Seyfried "If your lighter runs out of fluid or flint and stops making fire, and you can't be bothered to figure out about lighter fluid or flint, that is not Zippo's fault." -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org