Quoting Guido Berhoerster <gber@opensuse.org>:
That's likely, the relatively easy to find cases like libcanberra which is now built without gstreamer support or rygel which was the only case where both gstreamer version where directly linked to should be fixed now. If the problem cannot be fixed on the gstreamer side by using symbol versioning then we should at least make the effort to identify the issues within the distro. However that isn't straightforward as e.g. Firefox illustrates, any ideas how to address this systematically? There is also quite a few libraries which still link to gstreamer-0.10 like or QtWebKit some wxgtk stuff, it should probably be noted in the release notes that these must not be combined with gstreamer-1.0.
Indeed a good thing to document. And a clear action item for 13.1: we must make it a high prio target to eliminate Gst 0.10 from the tree (or, at least only provide it for convenience to 3rd parties... it's an unmaintained code base).
- Port apps to GStreamer 1.0 (as requested as target at the beginning of 12.3 cycle).
Ideal solution... But I don't think we have the resources for this. Not to mention Packman, which is not currently in it best shape.
Some packages like e.g. xfce4-volumed, xfce4-mixer, or gmixer also cannot be ported to newer gstreamer versions since the parts of the API they are built around were removed without replacement.
Talking to Gst upstream about this issue leads to the point that GstMixer was apparently heavily broken (it always depends on who you ask... seems the xfce devs were fine with it)_ and they recommend to use alsa / PA backends directly to get a sane code base... This for sure should not become a long-term blocker for the removal of Gst 0.10. Best regards, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org