Spec Name or Url: http://flyn.org/SRPMS/gstreamer010.spec SRPM Name or Url: http://flyn.org/SRPMS/gstreamer010-0.10.1-1.src.rpm Description: GStreamer is a streaming media framework, based on graphs of filters which operate on media data. Applications using this library can do anything from real-time sound processing to playing videos, and just about anything else media-related. Its plugin-based architecture means that new data types or processing capabilities can be added simply by installing new plugins.
This has made it into core already and will be built into rawhide tomorrow pending some issues with the 08 packages.
(In reply to comment #1) > This has made it into core already and will be built into rawhide tomorrow > pending some issues with the 08 packages. All well and good, but it would still be useful to have the package in Fedora Core 4.
(In reply to comment #2) > > All well and good, but it would still be useful to have the package in Fedora > Core 4. Yes it would. I agree DVD playback in totem does not work in FC4, for example - a gstreamer bug that is (supposedly) fixed in later gstreamer releases. Can this be re-opened for FC-4? I think it would need to be cooperating with the FC-5 developer to make sure that there isn't an FC-5 upgrade path problem (the fc5 gstreamer should obsolete/provide this one)
The dvdnav and dvdread plugins have not yet been ported to gstreamer010. So even if gstreamer010 was released for Fedora Core 4, the library would not provide a DVD capability. Also, the CVS version of totem is required if one is to use gstreamer010. I'm not trying to obstruct things, I just want to make sure people have realistic expectations. At this point, gstreamer010 is clearly not Fedora Core 4 material. The gstreamer010 platform looks great but it will be some time before the applications and plugins are ported to it.
Just to clarify comment #4: the gstreamer010 dvdnav and dvdread plugins can't be shipped as a part of Fedora proper (in addition to not existing yet.) See http://fedoraproject.org/wiki/FAQ/#head- b04c931c017de3facba9c69207925234df3c2232.