Package versions/builds in Conda env definition files

[kbseah]

When creating conda environemnt from envs/mb_taxonomy.yaml, the following error was reported:

CreateCondaEnvironmentException:
Could not create conda environment from /mnt/data/homes/seah/test_mb_pipeline/MB_Pipeline/envs/mb_taxonomy.yaml:
Encountered problems while solving:
  - nothing provides requested google-cloud-core ==1.7.1 pyhd3eb1b0_0

Dependencies in the Conda environment definition files are specified with version and build.

For at least one package, the specified build is not available from the listed channels (conda-forge, bioconda, r):

google-cloud-core=1.7.1=pyhd3eb1b0_0 is listed, but build for this version on conda-forge is pyh6c4a22f_0. The listed build pyhd3eb1b0_0 is available on main channel, though.

This may affect other packages in the pipeline too. Should we make it less strict and:

• Only list the tools directly needed, leaving the rest to environment solver
• Only pin the versions, not builds?

[kbseah]

Ideally we have a "minimal" conda env definition with only the relevant packages + versions

For archiving/reproducibility, use the snakemake --archive function and archive the tarball on Zenodo or similar, to safeguard against e.g. link rot.

[LasKru]

fixed with the merge #3