From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510 Galeon/1.3.14 Description of problem: [root@gruyere ~]# pkg-config --libs libdv sh: line 1: glib-config: command not found sh: line 1: glib-config: command not found sh: line 1: glib-config: command not found sh: line 1: gtk-config: command not found sh: line 1: gtk-config: command not found sh: line 1: gtk-config: command not found Package 'libdv' requires 'glib >= 1.2.4' but version of GLib is Please add "Requires:gtk+-devel" in libdv-devel requirement list in spec file. Version-Release number of selected component (if applicable): libdv(0:0.102-1).i386 How reproducible: Always Steps to Reproduce: 1. install libdv-devel 2. install pkgconfig 3. pkgconfig libdv --libs Additional info:
arg, build system failed, will probably build tomorrow
This actually isn't the right solution. It's actually a bug in the pkg-config file, libdv.pc, for libdv. It's fixed upstream. What happens in that the libdv people distribute a test application, playdv, which plays DV files. It depends on GTK+. Their build process incorrectly adds the GTK+ dependencies to the pkg-config file. Since we don't ship playdv, we shouldn't actually depend on gtk+-devel, and that's why rpmbuild doesn't pick it up. The right solution is to patch libdv.pc.in so that this doesn't happen. (Which they've already done in libdv CVS.) See the following mail message: http://sourceforge.net/mailarchive/forum.php?thread_id=4431792&forum_id=5458 As a side note, fixing this will fix the bogus gtk+ dependency in gstreamer-plugins, since gstreamer-plugins uses libdv
The only thing that needs to require GTK+ is libdv-tools, which already does, in other words.