About chromium packaging

[Kevin Kofler]

Jeremy Nouhaud wrote:
> According to this comment from Spot it is possible to make, I quote,
> "an rpmfusion addon package to replace the ffmpegsumo.so".

And that comment is incorrect (or at least poorly formulated and 
incomplete):
1. There is no "ffmpegsumo.so" in his package (nor in any other current
   Chromium package). That file name was dropped in Chromium 45. Now, FFmpeg
   is either static, or shared as libffmpeg.so (in a private library
   directory). spot's package uses the latter (shared libffmpeg.so).
2. I don't see how you would replace the library, given that it is in a
   private library directory, thus referenced using RPATH. The ld.so.conf.d
   trick (as in freetype-freeworld) does not work on RPATH'd libraries.
   Using Conflicts: could work if the library were in a subpackage, but it
   is currently not.
3. While replacing the library will work if you have a solution to "2.", it
   will not necessarily do what you want. Websites will not be able to
   detect that your browser supports patent-encumbered codecs (such as
   H.264). You have to recompile the entire Chromium with the
   proprietary_codecs compile-time flag to make that work. Otherwise, the
   codec can be decoded if it gets sent, but querying for codec availability
   uses a hardcoded list determined only by that compile-time flag (i.e.,
   one of 2 hardcoded lists, selected by the proprietary_codecs flag).

        Kevin Kofler