Hi Tim! I understand that the user can have multiple kernels installed. However, I am not sure if supporting multiple versions of a development package makes sense. After all, there can be only one header file matching i.e. #include <cpufreq> and only one library file matching -lcpupower.
If you really want me to use the versioned package names, then I will have to use the alternatives mechanism for handling which of the installed packages provides /usr/include/cpufreq.h and /usr/lib/libcpupower.so. This will increase the complexity and make the package naming incompatible with Debian. Do you want me to go this way? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1215411 Title: libcpupower.so is not installed from linux-tools (saucy) Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The patch for bug 1158668 installs cpupower_$(abi_version) command- line tool as well as libcpupower.so.$(abi_version). This isn't particularly suitable for projects that previously used libcpufreq and intend to migrate to libcpupower, because the libcpupower.so symlink is no longer installed. The command-line tools can also have symlinks (e.g. cpupower -> cpupower_$(abi_version)). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp