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

Autodetect the need for conda create --copy #3193

Closed
natefoo opened this Issue Nov 17, 2016 · 1 comment

Comments

Projects
None yet
2 participants
@natefoo
Copy link
Member

natefoo commented Nov 17, 2016

As discussed in the comments on #3105, we could pretty easily detect whether conda create --copy is needed when setting up (even cached) job conda environments by attempting a hard link and then using --copy if it fails, and avoid admins having to explicitly set it.

That said, using symlinks instead of --copy should be safe as of Conda 4.3, as per conda/conda#3308 and conda/conda#3870.

@natefoo

This comment has been minimized.

Copy link
Member

natefoo commented Apr 26, 2017

With mulled environments now we no longer make per-job conda env copies, so this is no longer needed.

@natefoo natefoo closed this Apr 26, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment