Use LicenseRef-IntelSimplifiedSoftware as SPDX identifier

[xhochy]

This allows us to differentiate the license of these packages from other proprietary Intel packages with a different license.

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• [ ] Reset the build number to 0 (if the version changed)
• [x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [x] Ensured the license file is being packaged.

[conda-forge-webservices[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).
• When defining a source/url please add a sha256, sha1 or md5 checksum (sha256 preferably).

[PaulKMueller]

I checked out the raw license files for the different builds locally. Intel Simplified Software License (Version October 2022) should indeed be the applicable license for all of them 👍 .

[oleksandr-pavlyk]

Should we expected "IntelSimplifiedSoftware" to be present in https://github.com/spdx/license-list-data/blob/main/json/licenses.json or is it a conda-specific token?

[beckermr]

We should not expect it to be there. The LicenseRef- syntax indicates a custom token.

[xhochy]

I'm also happy to change it to something else, as this can be an arbitrary string. I'm mostly interested in having a string that separates it from other Intel licenses.

[napetrov]

One note - one of the reasons that this license is not SPDX conformant - it's not stable license and get ongoing working updates - so current versioning is important.

So LicenseRef-IntelSimplifiedSoftware is fine as long as there is no goal for differentiating between particular versions

[xhochy]

Seems like it would be better to include the version then, too? Should I add a 2022 suffix?

[napetrov]

Seems like it would be better to include the version then, too? Should I add a 2022 suffix?

or even like Oct2022 - as technically there might be multiple updates during year. Hopefully this will not happen

[xhochy]

@conda-forge-admin please rerender

[xhochy]

Updated to the dated-license and CI has passed, I hope this is ready for a merge now.