I have read this question (Running Snakemake in one single conda env) but still have some doubt.
I am using the '--conda-prefix /some/dir' option and I have a rule in my snakemake file with the directive:
rule xxx: ... conda: "envs/some.yaml" ...
The first call of that rule will create the conda environment according to the yaml file in /some/dir/envs with some random name (in my case 'bf55a79e'). If I run the workflow in a different directory, the same conda environment (/some/dir/envs/bf55a79e) gets activated directly instead of being built again. So this is what I expected.
My question is:
- is there some way of skipping the building and specifying that rule xxx should use an already existing conda environment somewhere?
- does anyone know where the mapping between rule and directory gets stored?