Semantic versioning

[ImpPhil]

Intel Nuget package version numbers don't conform to semantic versioning standard causing package resolution issues.

Semantic versioning uses X.Y.Z with additional X.Y.Z-a.b.c. reserved to indicate preview/beta versions.  2030.0.0.25930 doesn't conform.

This intelmkl.redist.win-x64 has these dependencies

and since the dependent packages also have invalid version numbers Visual Studio throws these warnings

I can only suggest you switch to using for example 2030.0.25930.

[ShanmukhS_Intel]

Hi Philip,

Thanks for posting on Intel Communities.

NuGet packages fetch the dependencies with the approximate best match in case of any mismatch.

Thanks for the feedback, We are discussing your issue internally. We will get back to you soon with an update.

Best Regards,

Shanmukh.SS

[ShanmukhS_Intel]

Hi Philip,

As the same question has been raised on the below thread as well, could you please let us know if we could continue addressing this issue on the below thread and close this?

Reference URL:

https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/vzMul-performance/m-p/1441909#M34067

Best Regards,

Shanmukh.SS

[ShanmukhS_Intel]

Hi Philip,

We are discussing your issue internally. We will get back to you with an update soon!

Regrets for the delay in response.

Best Regards,

Shanmukh.SS

[ImpPhil]

To add to your discussion, several Nuget packages (I'm thinking MKL.NET and Mathnet-numerics ) use Intel MKL as a native provider.  Unfortunately they both use custom builds of MKL which means if my app uses both MKL.NET and Mathnet-numerics, I end up downloading two different builds of MKL, each taking ~200Mb. 

If you resolved this issue and https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/IntelMkl-redist-linux-and-osx-nuget-... then hopefully MKL.NET and Mathnet-numerics (and others) could reference your nuget package, which would simplify dependencies.

[ShanmukhS_Intel]

Hi Philip,

The first three components of the versioning can already locate the package and the fourth component is just an extension. Hence the existing versioning could not be considered a bug.

Best Regards,

Shanmukh.SS

[ImpPhil]

I disagree.  The semantic versioning standard is explicit that you should use Major.Minor.Patch only.  Since nuget uses this standard your Nuget packages should conform, or you get problems as shown below.  Your mkl package has a dependencies of 

If you released a new version of one of the dependencies that only incremented the 4th component then this won't be located correctly, as is the case here.

[ShanmukhS_Intel]

Hi Philip,

Thanks for sharing your feedback. We are discussing your issue internally. We will get back to you soon with an update.

Best Regards,

Shanmukh.SS

[ShanmukhS_Intel]

Hi Philip,

This is to kindly inform you that we are looking into your issue and will be back with an update soon. Apologies for the delay in response.

Best Regards,

Shanmukh.SS