martinpacesa / martinpacesa/BindCraft
Install fails if conda envs are not in CONDA_BASE
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 278
- PR merge metrics
- No merged PRs in 30d
Description
In this line the installation script incorrectly assumes that the BindCraft env must be under CONDA_BASE. This fails for any system where this is not the case. One example is environments where conda is installed for multiple users globally, with envs being created in users HOME directories:
source ${CONDA_BASE}/bin/activate ${CONDA_BASE}/envs/BindCraft || { echo -e "Error: Failed to activate the BindCraft environment."; exit 1; }
Please consider changing this. source ${CONDA_BASE}/bin/activate BindCraft should work
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open install_bindcraft.sh and inspect the activation command at line 59. Verify the installer activates the BindCraft environment by name rather than assuming it is under CONDA_BASE, and confirm installation works when Conda environments are stored elsewhere.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- anaconda, bash
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 85/100