http://bugzilla.novell.com/show_bug.cgi?id=561044 http://bugzilla.novell.com/show_bug.cgi?id=561044#c1 Stanislav Brabec <sbrabec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@novell.com --- Comment #1 from Stanislav Brabec <sbrabec@novell.com> 2009-12-07 17:56:15 CET --- None of libgst* libraries trigger installation of X11. These gstreamer-0_10-plugins-* modules trigger installation of X11, directly or indirectly: gstreamer-0_10-plugins-base: pango (obvious) video4linux (for XVideo X overlay support) ximagesink (obvious) xvimagesink (obvious) gstreamer-0_10-plugins-good: cacasink (indirectly from libcaca.so.0) cairo (obvious) pulse (indirectly from libpulsecommon-0.9.19.so) ximagesrc (obvious) gstreamer-0_10-plugins-good-extra: aasink (indirectly from libaa.so.1) gstreamer-0_10-plugins-bad: nassink (obvious, not in openSUSE builds) rfbsrc (explicitly required) rsvg (indirectly from librsvg-2.so.2) sdl (indirectly from libSDL-1.2.so.0) vdpau (obvious) gstreamer-0_10-plugins-ugly: none It is possible to split these packages to arbitrary sub-packages, e. g. gstreamer-0_10-foo, gstreamer-0_10-foo-x11, gstreamer-0_10-foo-pango, gstreamer-0_10-foo-gtk or so. To not miss the comfort, adding Supplements: packageand(foo|libX11...) can be considered. Notes: - There is a RPM sub-package dependency correctness checker somewhere in ancient gstreamer-0.8 spec files. GStreamer modules need a special care to verify correctness of dependencies. They can link not only to libraries, but also to symbols defined in other gstreamer modules. GStreamer module loader is capable to resolve them and load, but rpm is not capable to do see these dependencies. - Some distributions (e. g. Angstrom, Poky and other OpenEmbedded based distributions) use per-module splitting. It is easy with BitBake build system, but it would become a nightmare with rpm spec files. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.