Kent Fredric posted on Wed, 31 Aug 2016 03:11:07 +1200 as excerpted: > On Tue, 30 Aug 2016 09:37:51 +0200 Alexis Ballier <aball...@gentoo.org> > wrote: > >> Most are fixed, but for me this implies that the space for breaking >> users setup is much wider with bundled ffmpeg... > > But that fallout is limited to firefox. > > As opposed to "roll out ffmpeg 3 prematurely" which will break *more* > than just firefox.
Umm... you mean chromium, not firefox, correct? Because I checked a couple of the bugs wondering how on earth a chromium- bundled ffmpeg would bug out firefox, and they're definitely chromium bugs, generally build-related, not firefox. Either way, having to stick with an old and likely vulnerable browser because the new one won't build isn't a bug I'd like to have. (In fact, that's one reason I'm downloading my browser updates direct from upstream, now, at least firefox ebuilds can be far enough behind for even ~arch, that I get worried I'm risking my security due to browsing with an outdated browser with known flaws published for several days, long enough the bad guys are likely exploiting them! Yes, there's additional risk from running the same binary build everyone else is, but when it's days after the upstream update and security flaws notification, and there's no ~arch or even hard-masked ebuild for it, even in the mozilla overlay let alone in the main tree, on an app as security- critical as a browser...) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
