Red Hat Bugzilla – Bug 186463
openobex-devel: +Requires: libusb-devel bluez-libs-devel
Last modified: 2007-11-30 17:11:28 EST
Requires: bluez libusb
Which is bogus/not-required (at least when/if static libs at not in use, see
also bug #186460), and should be dropped.
If not dropped, then at least add to -devel:
Requires: bluez-libs-devel, libusb-devel
This should be reported to upstream, not here.
Alex, yes and no. The bluez,libusb dependancies are only extraneous if built
Regardless, there is a dependancy problem *here*:
1. either remove them from the .pc file (preferred)
2. add the dependancies to the -devel subpkg.
But why --without-static is needed?
See http://fedoraproject.org/wiki/Packaging/Guidelines, section labelled
"Exclusion of Static Libraries"
I'm not sure, but I think you're confusing pkgconfig dependencies and rpm
dependencies here. Openobex does need bluez and libusb pkgconfig files to build,
hence it specifes them in its own pkgconfig file.
Yes, openobex BR's bluez and libusb, but openobex.pc defines what is used when
apps are using openobex-devel, ie, what the -devel subpkg Requires.
You're definitely confusing rpm packages with pkgconfig packages. Read this:
"pkg-config retrieves information about packages from special metadata files. These files are named
after the package, with the extension .pc. ... The package name specified on the pkg-config command
line is defined to be the name of the metadata file, minus the .pc extension."
Q: What are the names for pkgconfig metadata files for bluez and libusb?
A: bluez, libusb - there's no "-devel" suffixes.
I'm sorry, bugzilla isn't the place for this discussion, and I'm done trying to
convince you. I just hope Harald understands it better than you do.
I guess the safest thing to do is simply add to -devel:
Requires: libusb-devel bluez-libs-devel
(Offtopic: just read on the rpm-devel mailing list recently that the latest
version of rpm has added the ability to automatically add to -devel pkgs
Provides/Requires extracted from pkgconfig files... way cool).
I've included some of this in my patch on bug 180935