| 1 |
On Mon, 4 Jan 2016 14:09:17 -0500 |
| 2 |
waltdnes@××××××××.org wrote: |
| 3 |
|
| 4 |
> On Mon, Jan 04, 2016 at 11:20:57AM -0600, »Q« wrote |
| 5 |
> |
| 6 |
> > AFAICT, details of the gstreamer bug itself haven't been made public |
| 7 |
> > yet, and nobody is sure whether the unmaintained 0.10 branch needs a |
| 8 |
> > patch. See <https://bugs.gentoo.org/show_bug.cgi?id=553742#c11> and |
| 9 |
> > the following comment. |
| 10 |
> |
| 11 |
> As pointed out in comment 12 of that bug, 1.x broke the 0.10.x |
| 12 |
> ABI/API and causes problems on Firefox. I use Pale Moon, a Firefox |
| 13 |
> fork, and it too will only build with gstreamer 0.10.x. |
| 14 |
|
| 15 |
I couldn't follow everything in the bug linked from c12; I've been |
| 16 |
using Firefox latest with gstreamer-1.0 for a while without problems, |
| 17 |
but maybe that's because I don't use libav. |
| 18 |
|
| 19 |
This probably won't affect Pale Moon at all, but Mozilla has gotten rid |
| 20 |
of gstreamer support in Firefox (not yet in released versions): |
| 21 |
<https://bugzilla.mozilla.org/show_bug.cgi?id=1234092> |
Archives