I'm afraid this is not a singular case. at least ncmpcpp fails to emerge because it does not find libmpdclient installed, I don't know much aboout configure scripts but I think most of them require pkgconfig to work properly. Not only ncmpcpp, which does. I claim that pkgconfig should be made part of system. System holds, to my opinion, all sorts of nonsense that I find very inappropriate, so something as fundamental as pkgconfig is the least that one could expect from that set. Reproducible: Always
Thanks for reporting. It is fixed in 0.5.7 which is going stable right now (bug #369335).
Don't you agree pkg-config belongs in system? We don't know how many of these errors go unnoticed because configure would not throw fatal errors in case of optional packages.
(In reply to comment #2) > Don't you agree pkg-config belongs in system? We don't know how many of these > errors go unnoticed because configure would not throw fatal errors in case of > optional packages. I don't agree with putting dev-util/pkgconfig to system which is only a DEPEND of packages because it would be useless for binary-only systems. Then --depclean wouldn't be able to remove it, and it's depends, like dev-libs/glib:2. Packages should just have proper deps.
