attention open source people

[waider]

If you require package X for your code to compile, and package X goes to the trouble of providing either a pkg-config interface or a X-config interface, USE THE GODDAMN THING ALREADY. I'm fed up with packages that complain they can't find header files because they're simply not including the necessary CFLAGS as provided by X-config --cflags or whatever.

Oh, and while you're FIXING YOUR BROKEN BUILD can you either fix up or delete that .spec file you built three releases back which is now out of date? It's no big deal, it just makes me that bit more irritated.

Bloody kids. In my day...

Comments

[mskala.livejournal.com]

That goes double for X=freetype2. No, not all distributions install it by default. No, not all distributions that do install it by default install it in the same place. No, the place you think is the standard location for it is not where the filesystem standard says it should be, nor where it wants to install by default when installed from a tarball. No, not everyone who has freetype2 is using Linux or a "distribution" at all anyway.

And please do look for, and use if it exists, a pkg-config interface even if you think package X is still using X-config. You shouldn't stop being able to see X just because the maintainers of X upgraded to the new standard.

And pkg-config people: please make pkg-config recognize when it has been linked to the name X-config, and go into a compatibility mode, so that it'll be possible to work around people who didn't pay attention to my previous request. KTHXBYE.