On Sun, 28 Aug 2016 19:28:48 +0200 "Paweł Hajdan, Jr." <phajdan...@gentoo.org> wrote:
> See <https://bugs.gentoo.org/show_bug.cgi?id=591722> for context. > > chromium-54 is currently hard masked; it'd soon enter ~arch, and then > stable in ~6 weeks. ffmpeg-3.0.1 is currently hard masked. > > These are the options I see for how to proceed. Feel free to share > further alternatives. > > A. Prepare to unmask and eventually stabilize ffmpeg-3.0.1 Don't use 3.0. Go for 3.1.x. Except that, it's ideal, but revdeps need to be fixed somehow first. Help is actually deeply needed to push forward this agenda. Good news is that Toralf already ran the tinderbox on both ~arch and stable. Bad news is that there are a lot of failures. Some are not simple to fix. > B. Backport just the changes needed for chromium to older ffmpeg I doubt that is sanely possible. > C. Mask chromium's system-ffmpeg flag when the dependency on > ffmpeg-3.0.1 can't be satisfied It's a bad idea I think. > D. Patch chromium not to require newer ffmpeg Maybe the simplest temporary solution, it is equivalent to B. except we don't change every other consumer of the lib. In the end, I think if A. can't be sanely achieved, D. is the only option. Any clue on what chromium requires from 3.x+ ?
