GNOME Bugzilla – Bug 328141
Use Requires.private in pkg-config files when appropriate
Last modified: 2015-04-30 16:32:54 UTC
Pango has a heck a lot of pkg-config files. They should use Requires.private when it makes sense, like for gmodule... The infrastructure can be copied from cairo. It needs some hacks to configure.in to ensure that the pkg-config version supports Requires.private... For bonus move all these pkg-config files into a subdir.
Note that Pango already goes to quite a bit of length to get the *effect* of Requires.private (and better, because of it hacks the generated libtool files as well), without the requirement on a newish package so this mainly is a cleanup issue, and also, less importantly, would help when building static libraries. (But who does that?)
Isn't that only true about .la files that Fedora doesn't install anyway? All dependencies are there in pango.pc. What am I missing?
Well, pango.pc doesn't have interesting dependencies. Look at, say: $ pkg-config --libs pangoxft -lpangoxft-1.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 Note that Xft, Xrender, FreeType, etc, aren't there. Yes ... .la files aren't installed in Fedora, but Fedora is only part of the world :-)
Well, I think that's interesting. Why does that need to emit anything other than "-lpangoxft-1.0"?
Fixed in master.