Randy McMurchy wrote these words on 08/31/07 09:11 CST: > Dan Nicholson wrote: > >> I think that's true (if you're using the gstreamer backend and not the >> xine backend in totem). We should probably check that `gst-inspect >> gconfelements' returns successfully for totem. Or just Recommend the >> GConf dependency in gst-plugins-good since I'm pretty sure most of the >> gstreamer using GNOME apps leverage these plugins. > > I think that if we put "(required > if you plan to install Totem using the GStreamer backend)" after > the GConf dependency, it would give enough information.
And probably expand a bit as Dan explains above that other GNOME apps can leverage the GConf plugin. > That way if someone doesn't install GConf before gst-plugins-good, > at least we documented the requirement. > > Additionally, Totem should probably have a short para after the > dependencies saying that the GStreamer backend is the default now, > and you must ensure gst-plugins-good was built with GConf support > (use gst-inspect gconfelements to test). I'd like to go ahead and fix this issue. Upon thinking about it, I'm wondering if BLFS should recommend to use the Xine backend for Totem, as it appears it is more stable than the GStreamer backend. BLFS-6.3 is going to be released ASAP. So, the version of GConf, Totem and Gstreamer in the book now is likely to be the versions released with BLFS-6.3. Should we recommend what we know to be a more reliable version of Totem (built with Xine)? I think we should, but I'm soliciting comments. -- Randy rmlscsi: [bogomips 1003.23] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 21:55:01 up 5 days, 21:57, 1 user, load average: 0.07, 0.02, 0.00 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
