Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: lsstsw
-
Labels:None
-
Team:Architecture
-
Urgent?:No
Description
I found out that executing loadLSST.bash twice causes the wrong miniconda bin path to be exposed to the shell. This is because here the base miniconda bin directory is prepended to the PATH, however if the virtualenv has already been activated, it does not activate again and the miniconda bin shadows the virtualenv bin path and this means different modules are available than expected.
I'm pretty sure that line can simply be removed since the source activate should set the correct path in any case. If it cannot be removed, it should be an append so that sourcing the file multiple times does not end up in a confusing state.
FWIW, I think this is also a problem for the other shell specific files, but have not checked for sure.
Without that PATH entry, though, the user has no way of finding the activate script. So I think the proper replacement is to remove the PATH setting and instead have
source ${miniconda_path}/bin/activate "\${LSST_CONDA_ENV_NAME}"
Can you try this and see if it works for you?