Explicit environment file
Currently, we manage the conda environment via the install/recipes/iota2/meta.yaml
file. For development branches, we must manually install the dependencies added since our iota2 install from the conda repository:
#317 (comment 1117119)
As long as a new environment is not released, you must manually install the last three packages to use develop branch
This can be a bit cumbersome to do on multiple machines (e.g. laptop, cesbiocalc, hal). A better way would be to track a file like the one produced by conda list --export
which can be used directly to create an environment with conda create --name <env> --file <file>
or to update an existing environment with conda env update --file <file>
.
One benefit of this is to avoid to redo the dependency tree resolution which can be quite long (even with mamba) since the version of each package of the dependency tree is written explicitly. This is like the Project.toml
/Manifest.toml
in Julia packages for those who know.
related to #412 (closed)