On 27 November 2013 12:12, Andrew Wafaa <awafaa@opensuse.org> wrote:
On 27 November 2013 11:50, Raymond Wooninck <tittiatcoke@gmail.com> wrote:
On Wednesday 27 November 2013 11:47:46 Andrew Wafaa wrote:
Rather than perpetuate the discussion as IANAL, I recommend sending this over to Ciaran Farrell as he is indeed a lawyer (one of SUSE's fine legal team). Let him advise what can and can't be done from a legal perspective.
Hi Andy,
The original bug report was assigned to Ciaran and he came back that we can not build those codecs.
So I guess that's it.
Unfortunately that does seem to be the case then, either work around the codecs - which you have already cautioned against; or remove it completely from OBS and build it in Packman. It's a shame that those are the options, but we have to play the cards we are dealt :(
I replied in the bug report. AFAIS: Chromium just includes an internal copy of ffmpeg. This copy has the same restrictions than the normal/system one. Nothing to see here, really. The Chromium package in 12.3:Update and 13.1 compiles this copy with H.264 support, this needs to be fixed. If you want H264 support you just need to do the same than with the normal/system library: Substitute the internal copy for a version from Packman (or just delete it and it will use the system version). The only thing to consider is that it doesn't make sense to include a copy of ffmpeg only inside Chromium (in %{libdir}/chromium/). If we are going to include a copy of ffmpeg better to include a system/global one and let Chromium (and every other package) use it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org