Overwrite the `libcuda.so` symlink if present

jakirkham commented 5 years ago

As the libcuda.so symlink could have been added during a previous activation (and deactivation may not have occurred yet, like logging out), the symlink may already be there when we try to create it. In this case, just go ahead and forcibly overwrite the symlink with a new one.

Checklist

[x] Used a 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)
[ ] 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.

Note: Re-rendering is currently broken for this feedstock. ( https://github.com/conda-forge/nvcc-feedstock/issues/18 ) So not handling that in this PR.

conda-forge-linter commented 5 years ago

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.

kkraus14 commented 5 years ago

@jakirkham so if I'm understanding this correctly this is to protect against say:

$(base) conda activate environment_1
$(environment_1) conda activate environment_2

Where both environment_1 and environment_2 have the nvcc package?

jakirkham commented 5 years ago

Almost. It protects against this. Possibly with other steps in-between.

conda activate environment_1
conda activate environment_1

conda-forge / nvcc-feedstock

Overwrite the `libcuda.so` symlink if present #17