Added LICENSE file

[mmccarty]

Checklist

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

[conda-forge-linter]

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

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[jakirkham]

Hi Mike, thanks for the PR

Can you please share some more context about this? The source code already contains the license file, which we include in the packages here

[mmccarty]

Thanks @jakirkham Sorry, I meant to add context but got distracted. Someone pointed out to me that the license linked from https://anaconda.org/conda-forge/cuda-python results in a 404. I believe the license_file in recipe/meta.yml is relative to the recipe directory. Adding the file there should fix it?

[leofang]

@mmccarty If you're referring to the hyperlink LicenseRef-NVIDIA-SOFTWARE-LICENSE, you should just add one more entry license_url to meta.yaml pointing to CUDA Python's license page. This will not work.

[jakirkham]

Thanks for the context Mike. No worries 🙂

Agree with Leo. Would also suggest re-rendering after making that change.

[leofang]

ex: https://github.com/conda-forge/cusparselt-feedstock/blob/a38651f7ee8ce4182376664bc7215df842d1326a/recipe/meta.yaml#L71

[leofang]

@jakirkham That said, I do notice a few other feedstocks have incorrect hyperlinks too, even though license_url has been added:

• https://anaconda.org/conda-forge/cusparselt
• https://anaconda.org/conda-forge/cuquantum

However, the license link of cuTENSOR (https://anaconda.org/conda-forge/cutensor) works. I suspect it has to to with the "LicenseRef-" prefix that we added to suppress the linter complaint (when cuTENSOR was added to conda-forge, it started without the prefix; it's added later after the initial package already lived on anaconda.org). I think there is a bug somewhere in anaconda.org's hyperlink handling (as I checked and didn't spot anything odd in conda-build or conda-smithy).

[jakirkham]

Could you please raise new issues on those feedstocks regarding these links?

[mmccarty]

@conda-forge-admin, please rerender

[mmccarty]

@leofang @jakirkham Looks like that did the trick. At least for the ReadMe. Thanks!

[leofang]

Could you please raise new issues on those feedstocks regarding these links?

Thanks @jakirkham for a few good catches, I narrow it down to this list:

• License hyperlink on anaconda.org not working cusparselt-feedstock#14
• License hyperlink on anaconda.org not working cuquantum-python-feedstock#4
• License hyperlink on anaconda.org not working cuquantum-feedstock#3

[jakirkham]

Thanks Leo! 😄 Will follow up in those issues

[leofang]

Let's see if this change would get the hyperlink fixed on anaconda.org! (My guess is it would not.)

[jakirkham]

If it doesn't, let's open an issue on this feedstock and we can go from there

[mmccarty]

Looks like it's still broken. Opened an issue #7