-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/29/2012 03:56 PM, justin wrote: > On 29/11/12 14:16, hasufell wrote: >> >> again, even if there are corner cases which cannot be dealt with >> in a different way... >> >> having an eclass function like the mentioned one is bad, cause >> it suggests that this is a way to fix things. It's not. >> Application developers running gentoo might think "oh great, >> there is a pkgconfig file for this, so I can use it in my >> Makefile". Then a Fedora packager comes across this package and >> realizes a compile failure until he notices the build system is >> calling for a pkgconfig file that cannot be found anywhere. So he >> contacts this developer and asks which distro he is using. > > So why not making our lives easier by having a pkg-config option?
Did you read what you quoted? Are you saying cross distro interfaces for accessing libraries in build systems are ok to break? Not only are people using foo.pc to compile a package on gentoo, but also when writing a build system for "bar" which might link against "foo". So having largely unused .pc files is the best case, the worst is causing random breakage/annoyance for other distros without even knowing, cause yeah... for us it works. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQt4wFAAoJEFpvPKfnPDWzVRYH/1GEU5z5wPiNbruYJYrRDFD5 ttjclvPYDsx+4XOjl7ppFS8LsnYr6GQu6qMFC33G6jQyj+lFR/OAzW35aAoa4PDc IzduHa5auP853Kscj+Qx/HHTakm1CCLq8tTjFdiHjlh0khHrTqdH/EdLMqxL9fYq l64wTmXMpwvg11jAd6mEV1kX8+LR1gV6ksE3FPNIuBiiVzYfiqYzsSJa5OuGSQ7X US+krpAXpFb4bvaGRKuhBHa1SOWinUSIPmk6C01faLEbhI4g/DQp6G0NBQPpN4Nh ivMQGo1qWJjUQvcS2BDApeA3R6LLyCczxsYkkXK3czneAMwbaUUoBZwczrRPcQQ= =qZ9+ -----END PGP SIGNATURE-----
