Skip to content

Install fails if conda envs are not in CONDA_BASE #368

@FlyinTeller

Description

@FlyinTeller

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions