After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 621362 - should not depend on gconf
should not depend on gconf
Status: RESOLVED NOTGNOME
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
0.10.23
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-12 11:27 UTC by Alexander van Loon
Modified: 2010-09-05 14:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexander van Loon 2010-06-12 11:27:25 UTC
Please see https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base0.10/+bug/590077

The package gst-plugins-good depends on gconf, which is a part of GNOME. I thought GStreamer wasn’t tied to GNOME, and it’s also supposed to be used in conjunction with other desktop environments such as KDE. In that case, it’s very unfortunate that I’m forced to pollute my KDE installation with GNOME software. I hope something can be done about this, can GStreamer be made to no longer depend on any GNOME software?
Comment 1 Sebastian Dröge (slomo) 2010-06-12 11:46:57 UTC
The GConf plugin is completely optional. If anything your distribution should decide to split the gconf module in a different binary package to not force KDE users to install gconf.
Comment 2 Tim-Philipp Müller 2010-06-12 11:49:32 UTC
GStreamer does not depend on GNOME. The only hard dependency is GLib really (and Qt on Linux depends on that too, as far as I know).

This looks more like a packaging issue to me. If Debian/Ubuntu chose to package gst-plugins-good in such a way that it depends on gconf (instead of splitting gconf-related things into a separate package), there's not much we can do about that. Same for most other dependencies.

I believe gst-plugins-good from source can be compiled just fine without anything gconf-related installed (and passing --disable-gconf and --disable-gconftool to configure will disable this even if gconf-related items are installed).

In short, this very much looks like NOTGNOME to me.
Comment 3 Alexander van Loon 2010-06-12 15:32:23 UTC
Thank you both for your quick replies. I’ll file a bug on Debian’s bug tracker then.
Comment 4 Alexander van Loon 2010-09-05 14:40:09 UTC
Filed the bug on Debian’s bug tracking system: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=595651