On Tue, Apr 05, 2005 at 03:42:03PM -0400, John Thacker wrote: > The other, slightly nastier problem: Several packages allow one to > build with either gtk+ or gtk2. In Core, we're building with gtk2, > but these packages have to BuildRequire: gtk+-devel, which pulls in > the rest of the gtk+ stuff, in order to compile. This is because the > various auto* scripts pull in gtk+ macros. I *think* there are some > packages still like this in Core; I know I've run into it in the last > couple months, and have gotten used to pulling in gtk+ in order to > build, then removing it, when I want to rebuild a package. Ah, remembered one of the examples. xcdroast won't build without gtk+ installed, even though it only links against gtk2. That's because it can be built against either, and the use of various auto* macros. Of course, xcdroast also has this big honking error which was fixed in FC3 but the patch applied in FC3 is still left out of the devel package: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=134334 I rebuilt it myself after doing the trivial work necessary to apply the patch; that's why I found that it requires gtk+ installed. (The actual RPM BuildRequire is on gdk-pixbuf-devel, which yoinks the rest in.) John Thacker
Attachment:
pgpMYwO6FRE6Y.pgp
Description: PGP signature
