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. This already happened for me multiple times and the answers was "debian". All this sounds like a very dirty workaround and if you need it, then do it, but _don't_ create an eclass, cause it's not a good thing to standardize. These files should _not_ be distro-dependant. Try to find other solutions. -1 for this eclass
