What's the point of being able to install gstreamer version 0.8.1 if you can't using it with totem. gst-player, etc, both of which portage will only build with gstreamer 0.6.4? Reproducible: Always Steps to Reproduce: 1. emerge gstreamer (it installs version 0.8.1) 2. USE="gstreamer" emerge totem Actual Results: It wants to install and use gstreamer 0.6.4 instead :( Expected Results: It would be great if totem and other ebuilds with the gstreamer USE flag depended on >=0.6.* (rather than =0.6.*) for those that want to test 0.8.*. Another obstacle to testing gstreamer and gst-player 0.8.* is that the ebuilds for gst-plugins-colorspace and gst-player are old and still depend on gstreamer-0.6.4. I tried editing the gst-player and gst-plugins-colorspace ebuilds, but when I finally got it working, the divx movie I tested it with played only audio, no video. I tried adding divx to the GST_PLUGINS_BUILD variable in the gst-plugins-xvideo ebuild, but it didn't seem to help. In summary, what I'm begging for is a totem ebuild that allows versions of gstreamer greater than 0.6.* (like 0.8.1), and a gst-player-0.8.0 ebuild even if it's masked, as long as it's there.
builds have =gstreamer-0.6* for a reason. The gstreamer backend for that version only works with the 0.6 series. This is probably a dupe since there have been other reports asking for a totem updgrade. Here is an example: http://bugs.gentoo.org/show_bug.cgi?id=53184
I see. Then should I start a new bug about gst-player and gst-plugins-colorspace?
they won't be a priority since no packages depend on them
Oh well. Maybe I'll try building it manually without portage. So how do I close this bug then? I would select "Resolve bug, changing resolution to ", but then I don't know which status is appropriate to select there... maybe "INVALID" or "LATER"?
INVALID : this is no bug. Don't set severity next time please, setting blocker for this is insane.
