https://bugzilla.novell.com/show_bug.cgi?id=847971 https://bugzilla.novell.com/show_bug.cgi?id=847971#c11 Cristian Morales Vega <christian.morales.vega@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |christian.morales.vega@gmai | |l.com --- Comment #11 from Cristian Morales Vega <christian.morales.vega@gmail.com> 2013-11-27 12:17:42 UTC --- I don't use Chromium, and it's the first time I listen about "ffmpegsumo". But since this reached the mailing list and I would like it to stop, and had a quick look into it. So, correct me if I am wrong: a) libffmpegsumo is just libavutil + libavcodec + libavformat build into a single library b) If libffmpegsumo is not available, the libavutil + libavcodec + libavformat from the system will be used. This is specified in media/base/media_posix.cc: --------------------------------------------------------------------------- bool InitializeMediaLibraryInternal(const base::FilePath& module_dir) { StubPathMap paths; // First try to initialize with Chrome's sumo library. DCHECK_EQ(kNumStubModules, 1); paths[kModuleFfmpegsumo].push_back(module_dir.Append(kSumoLib).value()); // If that fails, see if any system libraries are available. paths[kModuleFfmpegsumo].push_back(module_dir.Append( FILE_PATH_LITERAL(DSO_NAME("avutil", AVUTIL_VERSION))).value()); paths[kModuleFfmpegsumo].push_back(module_dir.Append( FILE_PATH_LITERAL(DSO_NAME("avcodec", AVCODEC_VERSION))).value()); paths[kModuleFfmpegsumo].push_back(module_dir.Append( FILE_PATH_LITERAL(DSO_NAME("avformat", AVFORMAT_VERSION))).value()); return InitializeStubs(paths); } --------------------------------------------------------------------------- c) libffmpegsumo has never depended on ffmpeg libraries. To have full multimedia support you need libffmpegsumo from Packman, not just ffmpeg. If so, IMHO there is no problem here. Just build the Chromium/libffmpegsumo version in openSUSE without the extra codecs (ffmpeg_branding != Chrome). And leave "proprietary_codecs" enabled (since it only affects what Chromium *claims* to support). Optionally, build in Packman libffmpegsumo with all the codecs supported. Result: - Chromium and libffmpegsumo from openSUSE Only "open" codecs are supported - Chromium and no libffmegsumo/ffmpeg libraries installed No codecs support at all - Chromium and libffmegsumo from Packman Full codecs support - Chromium and ffmpeg libraries from Packman (supposing they are compatible), with no libffmpegsumo at all Full codecs support The only question is how Chromium will behave when it claims to support a codec that it can't support. But I guess it will not be any user visible change. -- 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.