I just had some minor trouble with gst-plugins-bad-0.10.23-r1. I asked the upstream devs about it and was told that gstreamer 0.10.x had been abandoned. According to the main repo, 0.10.x and its plugins are 1-1.5 year old animals. I use Opera and learning that it uses such long-untouched code doesn't make me feel good about browsing outside http://localhost, so to speak. There are other concerns besides security, obviously. For an amd64 hardened system there 105 stable package-ver.si.ons (excluding gst components themselves) in the tree that depend on media-libs/gst* or media-plugins/gst*. 80-100% of them declare dependency on the 0.10 gst slot. Meaning a lot of packages are affected. Please consider starting a tree-wide port to gst-1.x. gst-1.0 is only about 6 months old, but I assume most packages (at least the important ones) have adapted to it by now. Reproducible: Always
:roll: Depends. Would you count mozilla family as important packages ? That's still on 0.10 and they're notoriously late with adapting new libs / dropping the old ones (well, unless you count those they bundle). Regarding opera, it's proprietary, so it can be changed only by its upstream - though this one it a bit unpredictable, with its plans to switch to webkit. Also, I might not be quite up to date, but gstreamer herd has been suffering from lack of time/people for quite awhile. The bottom line is, that 0.10 to 1.0 migration of any package is an upstream decision anyway.
In case the dependencies on gst-0.10 are inevitable for all the software to run, then it's a sad story and the case can be closed, of course. Are you sure about that or are you speculating? I just didn't see that coming, so I didn't even test anything. I guess I'll check if some of the key stuff is willing to compile against gst-1.x.
You were right, qt/wine/bluez need 0.10. FF talks like it's OK with 1.0 in configure, but no.
