1 |
Duncan <1i5t5.duncan@×××.net> wrote: |
2 |
> |
3 |
>> Alexis Ballier <aballier@g.o> wrote: |
4 |
>> |
5 |
>> As opposed to "roll out ffmpeg 3 prematurely" which will break *more* |
6 |
>> than just firefox. |
7 |
> |
8 |
> Umm... you mean chromium, not firefox, correct? |
9 |
|
10 |
I also think so. I have unmasked ffmpeg-3 since several months, |
11 |
because I don't use any package from bug 574788, but instead >gcc-5. |
12 |
Everything for which I (and I suppose most people) need ffmpeg |
13 |
compiles (and so far runs) without any problems: |
14 |
libquicktime, xine-lib-1.2.6-r1, mplayer-1.3.0, mpv-0.19.0, |
15 |
handbrake-0.10.5-r1, firefox-48.0, avidemux-2.6.8 |
16 |
|
17 |
(Well, for the apparently maintainer-needed avidemux I had lately |
18 |
to do a version bump to 2.6.12 and some patching in the mv overlay; |
19 |
but this was only for the very latest bump of ffmpeg-1.3.2 -> 1.3.3 |
20 |
plus a simultaneous bump gcc-5.4.0 -> 6.2.0. I didn't check whether |
21 |
the ffmpeg bump was related here, at all, or whether a similar |
22 |
patching could have been done for avidemux-2.6.8) |