https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c3 --- Comment #3 from Ignacio Areta <areta@outlook.com.br> 2013-11-22 00:54:22 UTC --- (In reply to comment #2)
Ignacio, Thank you for the support that I am receiving from you. It seems to me that you are much better off with using the official Chrome package. At least there the packager is not "PLAYING" with all kind of flags in order to get a full working browser with all codecs supported.
Please don't comment just you found something on a wiki side, without knowing why these flags have been set. If you install the corresponding chromium-ffmpeg package from Packman, then the Chromium is providing this full support.
Those two flags are required to have full support for those codecs in Chromium. I can leave them out, yes, but that would mean that the Chromium package will never support H.264 nor mp4, etc. Whether you install the chromium-ffmpeg package from packman or not. At that moment you would be forced to switch to the official Chrome package.
This has been the situation ever since Chromium was build for openSUSE. Also your last paragraph shows how much you understand the package as that those codecs are shipped through the ffmpeg package on Packman. The ffmpegsumo package that comes with openSUSE actually only support the opensource codecs. So the proper bug report would be that chromium without the anything from Packman pretends to be able to play certain proprietary codecs which it actually can't.
From my point of view, to avoid chromium-ffmpegsumo from opeSUSE reproducing
I know why these flags are present. But... Re-read the bug report, re-read my comment. The bug report tells that chromium-ffmpegsumo from openSUSE is reproducing MP3 audio and MP4 video. And this occurs because these flags are present. If you have a scipt/patch/whatever to avoid the openSUSE's chromium-ffmpegsumo reproducing these formats, that script/patch/whatever isn't working. You marked this as wontfix. But did you try to reproduce this? No? So, install chromium-ffmpegsumo from openSUSE, enable HTML5 on YouTube and try to go to the links in comment 1, click with the right button on the video > Statics for nerds and see what's happening. Also, try this link too. I reproduced with suceess the MP3 file. http://hpr.dogphilosophy.net/test/ Get the fact: chromium-ffmpegsumo from openSUSE is reproducing MP3 and MP4 files, and not only showing them as supported. 2 users reproduced this bug with sucess. And chromium-ffmpegsumo from openSUSE is reproducing these files because of these two flags. So, closing this bug as wontfix can be risky to the future of Chromium in openSUSE. these formats, the solution is to not use these flags. Do you have another idea?
But hey, if you have the feeling that you can provide a better Chromium package, that you are more than welcome to take over the maintainership.
I was doing some research about this some months ago because at that time there wasn't a stable version of Chromium at openSUSE. But as you started to package the stable version, I abbandoned the idea. But I can consider this again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.