Re: About chromium packaging

On Sun, Aug 7, 2016 at 5:56 PM, Kevin Kofler <kevin.kofler(a)chello.at&gt; wrote: > Hans de Goede wrote: >> <sigh> I don't understand why you keep repeating this. I'm sure we can >> come-up with a patch to make the codec-lists a runtime configurable >> thing, this is not rocket science. > > If you want to have a try at fixing this, look, e.g., at the member variable > media::MimeUtil::allow_proprietary_codecs_, i.e., the way it is initialized > (to a compile-time hardcoded value) and the way it is used (in several > places). > > The right way would really be to remove the boolean variable (which only > allows a binary all-or-nothing approach to patent-encumbered codecs) > entirely and query for each individual codec at runtime. But then, you will > likely be querying FFmpeg directly, whereas for Samsung's GStreamer backend > (which is also affected by this issue, see > https://github.com/Samsung/ChromiumGStreamerBackend/issues/16 ), one would > have to query GStreamer directly instead. You would also likely be touching > several code places related to codec support. > > A less invasive approach would simply try to initialize > media::MimeUtil::allow_proprietary_codecs_ to a runtime-detected value.