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

hardcoded: export condaname="fermitools" in activate.sh #163

Open
mireianievas opened this issue Apr 11, 2024 · 1 comment
Open

hardcoded: export condaname="fermitools" in activate.sh #163

mireianievas opened this issue Apr 11, 2024 · 1 comment
Assignees

Comments

@mireianievas
Copy link

I just noticed there is a hardcoded line

export condaname="fermitools"

in the activate.sh

If you create the environment with a different name, it will fail to activate the conda environment.

@donhorner donhorner self-assigned this Apr 12, 2024
@donhorner
Copy link

How are you creating your environment? I don't have any problems creating conda Fermitools environments with different names, and we've never had a report from a user with that problem.

The condaname in the activate.sh file just sets a directory name. I assume it's based on the installed conda package name(fermitools for Fermitools). The environment name is in $CONDA_PREFIX, so activate.sh sets paths like: export INST_DIR=$CONDA_PREFIX/share/${condaname}
which in my current conda environment ("fermi220") is:
~/miniconda3/envs/fermi220/share/fermitools

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

No branches or pull requests

2 participants