Comment 26 for bug 1215411

I understand, I just don't see how we can achieve this. You can have multiple linux-tools packages installed and you'll get different versions of libcpupower. We don't guarantee ABI stability so your running app needs to be linked to the version of the running kernel or it might no longer work.

I just checked Debian and there you can have 2 different versions of libcpupower installed as well and depending on which is installed, the generic link points to a different (kernel) version of libcpupower. How is this expected to work if the ABI is different between the two versions?

$ dpkg -l libcpupower-dev
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============-===============-============-=====================================================================
ii libcpupower-dev 5.2.9-2~bpo10+1 amd64 CPU frequency and voltage scaling tools for Linux (development files)

$ ls -l /usr/lib/x86_64-linux-gnu/libcpupower.so*
lrwxrwxrwx 1 root root 20 Aug 25 17:28 /usr/lib/x86_64-linux-gnu/libcpupower.so -> libcpupower.so.2.0.1
-rw-r--r-- 1 root root 26840 Aug 28 04:20 /usr/lib/x86_64-linux-gnu/libcpupower.so.0.0.1
lrwxrwxrwx 1 root root 20 Aug 28 04:20 /usr/lib/x86_64-linux-gnu/libcpupower.so.1 -> libcpupower.so.0.0.1
lrwxrwxrwx 1 root root 20 Aug 25 17:28 /usr/lib/x86_64-linux-gnu/libcpupower.so.2 -> libcpupower.so.2.0.1
-rw-r--r-- 1 root root 26840 Aug 25 17:28 /usr/lib/x86_64-linux-gnu/libcpupower.so.2.0.1