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
Allow conda activate to set its own PATH. #109
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks reasonable but it looks like it may somehow break the templating of loadLSST.bash
?
export LSST_CONDA_ENV_NAME=\${LSST_CONDA_ENV_NAME:-${LSST_CONDA_ENV_NAME}} | ||
# shellcheck disable=SC1091 | ||
source activate "\$LSST_CONDA_ENV_NAME" | ||
source "${miniconda_path}/bin/activate" "\$LSST_CONDA_ENV_NAME" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At some point aren't we supposed to be switching to conda activate
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll leave that modernization to someone else.
conda activate should do this for us.
@jhoblitt Indeed the point of this is to change the template output. I believe I have removed the test that no longer applies. |
@jhoblitt Some help with figuring out why the bash compile fails would be appreciated, though. The failure seems to be caused by the makefile looking for |
Looks like making the |
No description provided.