Update to 8.8.0.121 and add CUDA 12 support.

[bdice]

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.

This PR updates cuDNN to 8.8.0.121 with support for CUDA 11 and CUDA 12.

Fixes #54

[conda-forge-webservices]

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:

• Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

[conda-forge-webservices]

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.

[bdice]

@conda-forge-admin, please rerender

[github-actions]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/cudnn-feedstock/actions/runs/4791287396.

[bdice]

cc: @jakirkham @leofang @adibbley @robertmaynard for notice/review. I think CI should pass this round (still running).

[bdice]

(and thanks in advance to @kkraus14 as package maintainer for a review, as well) 🙏

[leofang]

Thanks, Bradley! LGTM except for one nit.

[leofang]

Q: Would it possible that we try moving ppc64le back to Travis? It is slightly stabler than before, so if it can complete aarch64 in less than 15 mins, it might work for ppc64le too. Not a blocking change, though, and I am no longer the maintainer here 🙂

[kkraus14]

I also, would like to no longer be a recipe maintainer for this package. Is there any chance someone else would like to be added? cc @adibbley

[jakirkham]

We were going to propose adding some folks here. Would suggest:

• @adibbley
• @bdice
• @jakirkham
• @vyasr

[jakirkham]

@conda-forge-admin, please re-render

[kkraus14]

Left one question about the dev package but otherwise lgtm. Thanks for taking over the maintenance of this package.

[jakirkham]

Thanks all! 🙏

Keith, could you please give this another look when you have a chance?

[kkraus14]

Ideally this cudnn package should probably be split into a runtime and dev package, where the dev package then makes sense to depend on cudart-dev

[bdice]

Ideally this cudnn package should probably be split into a runtime and dev package, where the dev package then makes sense to depend on cudart-dev

I think that is a good long-term plan. I'm hesitant to introduce that change right now, but the impact of that change can be surveyed and we can move in that direction over time. I'll file an issue.

edit: #57

[jakirkham]

Should add this same discussion came up offline previously and we decided to punt for now

[jakirkham]

Thanks all! 🙏

Going ahead and merging to get these packages out. Let's follow up on anything else separately 🙂