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?
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?