Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overwrite the libcuda.so symlink if present #17

Merged
merged 2 commits into from
Oct 16, 2019

Conversation

jakirkham
Copy link
Member

@jakirkham jakirkham commented Oct 16, 2019

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

  • Used a 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.

Note: Re-rendering is currently broken for this feedstock. ( #18 ) So not handling that in this PR.

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.
Now that we have changed how the activation script works, bump the build
number to create a new package with this change.
@conda-forge-linter
Copy link

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
Copy link
Contributor

kkraus14 commented Oct 16, 2019

@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
Copy link
Member Author

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

conda activate environment_1
conda activate environment_1

@jakirkham jakirkham merged commit 491bbcd into conda-forge:master Oct 16, 2019
@jakirkham jakirkham deleted the overwite_symlink branch October 16, 2019 16:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants