-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 28/11/12 08:26 PM, Richard Yao wrote: > On 11/28/2012 05:21 PM, Michał Górny wrote: >> On Wed, 28 Nov 2012 22:49:14 +0100 Justin <j...@gentoo.org> >> wrote: >> >>> Hi, >>> >>> and another one. >>> >>> Problem: Some packages aren't lucky and their buildsystem >>> doesn't create pkg-config files out of the box. >>> >>> Solution: Create them by hand. >> >> Result: packages which fail to build on distributions other than >> Gentoo because their authors were using Gentoo and didn't knew >> that the pkg-config aren't anywhere else. >> > > I suspect that the .pc files would probably be available if people > installed -dev packages. If not, people can blame the distribution > developers for breaking things. >
They wouldn't be if upstream doesn't provide them and only Gentoo did, which is what this eclass would be for.. Standard rules of development, if the lib doesn't provide a .pc file then you can't use pkg-config to configure your software for it. There's no point in providing a .pc file if nothing is going to use it, and we (gentoo developers) definitely do not want to end up patching and maintaining patches on both a lib and all its rdeps just so that it support pkgconfig. (i came across this situation already and learned a bit the hard way with spidermonkey. It sucked to have to use checks for filenames and special defines in header files to find the right libs, but that was still the only "right" way to do it until spidermonkey upstream finally started bundling a .pc) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlC3ZLkACgkQ2ugaI38ACPANHAD/RtWy8/K6U58PQWvk7CyfRSth 1WrlSwbjJslioWfaRvYA/RMnJX9/Js1YkYHZBGHk28dK2GzwrxJh872MqsCqWEVR =4EwJ -----END PGP SIGNATURE-----
