Fwd: building chromium against system ffmpeg (was: Distros and QtWebEngine)

Sat Apr 25 18:17:33 UTC 2015

----------  Forwarded Message  ----------

Subject: building chromium against system ffmpeg (was: Distros and 
QtWebEngine)
Date: Saturday 25 April 2015, 17:41:19
From: Andreas Cadhalpun <andreas.cadhalpun at googlemail.com>
To: Lisandro Damián Nicanor Pérez Meyer <perezmeyer at gmail.com>

Hi Lisandro,

I'm maintaining ffmpeg in Debian and just came across the thread about
"Distros and QtWebEngine" on kde-core-devel, where you wrote [1]:
> Actually when it comes to the web engine it's not true. When I suggested to 
> use an external ffmpeg and libv8 (javascript engine) the answer was directly 
> no, simply because they are too entangled to be possible. And ffmpeg tends 
to 
> be quite a source of CVEs...

As I understand it QtWebEngine embeds chromium (horrible idea),
which embeds ffmpeg (bad idea).
I just want to point out that it is possible to build chromium against
the system ffmpeg libraries, see bug #763632 [2].
(I did it and playing videos on youtube still worked, yay!)
This is not yet done, because ffmpeg wasn't allowed into jessie [3].

As for ffmpeg being a source of CVEs: I'm working on fixing that.
And by the way I doubt that gstreamer is any better security-wise,
rather the contrary, because most fixes don't get backported.

Best regards,
Andreas

1: https://marc.info/?l=kde-core-devel&m=142959920525945&w=1
2: https://bugs.debian.org/763632
3: https://bugs.debian.org/763148
-----------------------------------------
-- 
If you realize that you are in a hole... stop digging.
  Anonimous, thanks to ScottK.

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20150425/f9b26d07/attachment.sig>