pkg-config --modversion libproxy-1.0 - doesn't output the right version

[GoogleCodeExporter]

What steps will reproduce the problem?
1. pkg-config --modversion libproxy-1.0 once libproxy is correctly installed.

What is the expected output? What do you see instead?

It returns nothing in 0.4.4 version up to current trunk
It should return the version of the package (0.4.6 for the current stable 
version).
The problem is that checking the version of libproxy it is unreliable before 
any future version, whereas it should have been really trivial.

What version of the product are you using? On what operating system? Linux, 
Fedora 14,  cmake-2.8.2

Please provide any additional information below.
this problem was initialy reported here:
https://bugzilla.redhat.com/show_bug.cgi?id=656484

Thx

Original issue reported on code.google.com by kwiz...@gmail.com on 24 Nov 2010 at 9:55

[GoogleCodeExporter]

kwitzart, Thank you very much for your report.

In openSUSE, the following happens (with 0.4.6):
dle3ams@3120-3560:~/Documents/src/libproxy/libproxy> pkg-config --modversion 
libproxy-1.0
0.4.6
dle3ams@3120-3560:~/Documents/src/libproxy/libproxy> rpm -qf 
/usr/lib64/pkgconfig/libproxy-1.0.pc
libproxy-devel-0.4.6-54.3.x86_64

libproxy-1.0.pc.in contains Version: @PROJECT_VERSION@, which should be 
replaced by cmake when rewriting this file to libproxy-1.0.pc, which finally 
get's installed.

Do you have any additional tweaks in your package interfering with this? (I can 
believe there was an error in 0.4.4, but I do remember there was a fix to 
address this, see r716)

Original comment by dominiqu...@gmail.com on 24 Nov 2010 at 8:56

• Changed state: NeedInfo

[GoogleCodeExporter]

kwitzart confirmed that this is resolved, he gets a proper version as expected 
too.

Original comment by dominiqu...@gmail.com on 29 Mar 2011 at 6:26

• Changed state: Fixed