On Wed, Aug 31, 2016 at 8:06 AM, Alexis Ballier <aball...@gentoo.org> wrote: > > For years we've been patching packages to work with >= our latest stable > version of ffmpeg/libav and unbundle it. Even mplayer. Chromium shouldnt > be any exception. > > Patching consumer packages that way has some advantages: > - Maintainers do not need to wait for ffmpeg to be stabilized.
Sure, but we're talking about a major version here, and a web browser where future security updates need to be deployed quickly. You don't want to be stuck figuring out what other ffmpeg API calls were touched in the new version while there is some exploit floating around. It seems like bundling is the simpler solution here, unless the necessary patches are trivial. If they're in fact trivial somebody can probably just post one and save a lot of speculation. :) Ultimately though I think it is up to the chromium team to decide whether they would rather bundle or patch. Then perhaps the rest of us get to decide whether we want chromium in the tree or not. They're volunteers, after all, we can't force them to create patches. I suspect for quite a few Gentoo would probably go before Chromium does. -- Rich
