Remove version constraint of nvcc to match with host cuda version

[galipremsagar]

This PR removes the version constraint that nvcc imposes to have the matching CUDA version on the host machine installed. Upon some searching, relaxing & testing this fix it appears that there is no version-specific file being shipped along with nvcc conda package, but I could be wrong here too. Hence requesting review from maintainers since this check has been present since its inception.

Rationale behind this PR is to allow users to utilized any version of nvcc package without upgrading their local host CUDA installations.

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.

[leofang]

Not sure what you meant, isn't PKG_VERSION defined by conda-build?
https://docs.conda.io/projects/conda-build/en/latest/user-guide/environment-variables.html#environment-variables-set-during-the-build-process

[leofang]

We still need this check for building the nvcc packages. It can be a warning in user envs. I failed to recognize this is part of the activation script (it's super confusing we don't make activation/deactivation scripts standalone, see #68). @galipremsagar will make the change and I will continue #68 after this PR is merged.

[galipremsagar]

Synced offline with @leofang and agreed on erroring only during conda build time and just raising a warning for end-user during conda activation.

[jakirkham]

Would also bump the build number here

nvcc-feedstock/recipe/meta.yaml

Line 2 in 4acf86c

{% set number = 19 %}

That should generate new packages with this change

[galipremsagar]

Would also bump the build number here

nvcc-feedstock/recipe/meta.yaml

Line 2 in 4acf86c

{% set number = 19 %}

That should generate new packages with this change

Done 👍

[jakirkham]

Thanks Prem! 🙏 LGTM ✅

Will give others a chance to look 🙂

[leofang]

Thanks, @galipremsagar @jakirkham. LGTM.

[leofang]

Note to self: the extra backslash is needed because this is part of codegen, not the actual script.

[leofang]

To be eliminated in #91.

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[leofang]

Should we port this change to the Windows script?

[jakirkham]

Seems reasonable