-
Notifications
You must be signed in to change notification settings - Fork 88
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
conda-env create is using /tmp #1049
Comments
snakePipes config function needs to be modified such that it modifies |
As of 3.0.0 condaEnvDir should not be set in defaults.yaml anymore, but should be set in the appropriate profile (wherever that lives). As for the snakePipes config function, this would work, but do we still need a function that makes changes to these profiles to begin with ? |
Hi Ward, from my point of view, the user should be able to edit the config shipped with snakePipes. This is what the The documentation would also have to be updated, e.g. in the Best, |
Btw, |
Agreed for defaults.yaml, though note that profiles are allowed to live outside of the snakePipes directory (in a specific directory, or in the default locations that snakemake expects them to be, /etc/xdg/snakemake/ & ~/.config/snakemake/), and I think it's not so nice to change these files. If you insist of keeping that perhaps a comment line (# changed by snakePipes config) or something similar would be appropriate.. |
Ok to comment line after changing configuration. |
Makes sense yea, thanks ! 👍🏼 |
snakePipes 3.0.0 - snakemake is calling conda create env and pointing it to /tmp rather than to condaEnvDir defined in the defaults.yaml
The text was updated successfully, but these errors were encountered: