While app-crypt/qca-2.0.0-r2 installed it's packageconfig file into /usr/lib/pkgconfig/qca2.pc the new release app-crypt/qca-2.0.1 installs it's packageconfig file into /usr/lib/qca2/pkgconfig/qca2.pc This behaviour should be reverted, as this is just the wrong location for *.pc files and leads to problems, like current Kopete versions can't locate qca2.pc and fail to include support for it → no Jabber/Groupwise support. I couldn't find the actual reason for this behaviour yet. It's probably an upstream issue. Reproducible: Always Steps to Reproduce:
how bizarre. I'll look into it.
i added files/qca-2.0.1-pcfilespath.patch I ran out of time to work out how to regenerate the build system. if someone could commit that it would be great (with a revbump). need to report upstream too - email delta@lists.affinix.com if this works for you.
The *.pc file is still installed into the same location using this patch.
(In reply to comment #3) > The *.pc file is still installed into the same location using this patch. I know. I was hoping in comment #2 that the need to regenerate the QT build system was still required was clear. I don't have time currently. Answers here are welcome.
I can confirm the qca2.pc file is installed into the incorrect place.
Created attachment 164641 [details, diff] fixed patch.. instead of patch the qcm file, do the same for the configure file. since the qcm files seem not be read (they are read by qconf which is not in portage), this patch applies to the configure file.
Thanks Justin, Much appreciated. I've reported this upstream. Fixed in qca-2.0.1-r1 coming to a portage mirror near you.
*** Bug 236995 has been marked as a duplicate of this bug. ***
