Heads-up: Enabling generation of pkg-config requires

[Dan Nicholson]

On Sat, Nov 29, 2008 at 9:24 AM, Panu Matilainen
<pmatilai at laiskiainen.org> wrote:
>
> Just a heads-up, I'm (finally) enabling the generation of automatic
> pkg-config and libtool requires in rpm. Provides for these have been
> generated since first rpm 4.6.0 alpha hit rawhide, so with a bit of luck,
> all/most involved packages have been rebuilt since then and already have the
> needed provides for satisfying the new requires.
>
> But if you see unsatisfied dependencies on pkgconfig(foo) and libtool(foo),
> request a rebuild of the dependant package, that's all it should take.
> Except if you happen to hit a big chain of pkg-config using packages that
> haven't been rebuilt in several months, or bugs in the dependency
> generation, or buggy pkg-config .pc files...

Can I please take this opportunity to point out that the pkg-config in
fedora is broken specifically because of using pkgconfig autoreqprovs.
Specifically, this patch is used:

http://cvs.fedoraproject.org/viewvc/rpms/pkgconfig/devel/pkg-config-0.21-requires-private-fix.patch?view=log

This breaks the use of Requires.private in .pc files. The reason it
was added (as far as I can tell) is because the pkgconfig autoprovides
didn't take only added the Requires information. When package b has
package a in Requires.private, rpm does not add pkgconfig(a) as
required to package b. See this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=224148

And a follow up I opened which has patches which fix this:

https://bugzilla.redhat.com/show_bug.cgi?id=426106

Please, please, take a look at this. What fedora is doing is broken
and making it difficult for people that really want to use
Requires.private in their projects.

--
Dan