Right now it looks like MKL and MKL headers are not fully linked together with the versions that are allowed. That means I can imagine there being scenarios where a package requests both but has a compat bound on MKL forcing it to use an older version and gets the newest MKL_Headers package instead of the one for the MKL version requested.
I am not sure the best way of going about this though. One way is in the build script of dependent packages, but that would really need https://github.com/JuliaPackaging/BinaryBuilder.jl/issues/1212 to be implemented so MKL_Headers isn't installed on the end user machines. Would there be an equivalent way of linking these in the original builds?
Right now it looks like MKL and MKL headers are not fully linked together with the versions that are allowed. That means I can imagine there being scenarios where a package requests both but has a compat bound on MKL forcing it to use an older version and gets the newest MKL_Headers package instead of the one for the MKL version requested.
I am not sure the best way of going about this though. One way is in the build script of dependent packages, but that would really need https://github.com/JuliaPackaging/BinaryBuilder.jl/issues/1212 to be implemented so MKL_Headers isn't installed on the end user machines. Would there be an equivalent way of linking these in the original builds?