On 10 July 2013 12:54, Tomáš Chvátal
Hello guys,
I have created proof of concept libav library with disabled patented codecs in my home project [1]. This means that this library si up par with what we have in chromium and it should be legal to distribute.
Apart from the library the repo contains vlc chromium and xbmc (built localy fails on obs, meh) which seems to run fine, just not to play almost anything ^_^.
The possibility here is to include all the media players and stuff around it into openSUSE release, where one has to flip the switch in libav (see the spec file) and can build full-fledged-european-edition which can play our sweet movies.
Let me know what you think about this plan and what would you use as base devel project for this.
Cheers
Tom
[1] https://build.opensuse.org/project/show?project=home%3Ascarabeus_iv
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. 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. 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)? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org