reverse symlinks

[isuruf]

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.

Fixes #2

cc @peterbell10

[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.

[isuruf]

I moved these to the dev package, but I'm not even sure if these are needed at all.

[jakirkham]

Interesting given we already have these here and other packages have already built against cuda-nvtx, am a little hesitant to remove something that packages in user environments may already be depending on

[isuruf]

Reverted for now

[jakirkham]

Thanks for putting this together Isuru! 🙏

Would it be possible to configure CI to cache the packages so we can download them and do some tests? Maybe using azure/store_build_artifacts?

[isuruf]

@conda-forge-admin, rerender

[isuruf]

@jakirkham, you can check the artifacts at https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=825141&view=artifacts&pathAsName=false&type=publishedArtifacts

[isuruf]

Ping on this

[jakirkham]

Thanks Isuru! 🙏

Appreciate the reminder

Quoting @msarahan's recent reply ( #2 (comment) ):

We've been discussing this extensively internally and we definitely think it's a big issue, as it could affect CUDA libraries other than NVTX. The team is working on a document that details possible solutions in the context of CUDA library packages that exist in other forms. We'll file an issue in https://github.com/conda-forge/cuda-feedstock with more info when we've dug in more.