After installing micromamba (same with any flavor of conda), when my .bashrc loads I have an entry in my path like:
/home/users/balter/micromamba/condabin
It would be natural to think that this is the directory where one would find the conda executable, but not so:
balter@exahead1:~$ which micromamba
/usr/bin/which: no micromamba in (/home/groups/chse/Code/quality_measures:/home/groups/chse/Code/exacloud_utilities:/home/users/balter/micromamba/condabin:/home/users/balter/perl5/bin:/home/exacloud/software/spack/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/opt/ibutils/bin:/opt/puppetlabs/bin:/opt/dell/srvadmin/bin:/home/users/balter/usr/bin:/home/users/balter/bin)
balter@exahead1:~$ ls micromamba/
bin compiler_compat COPYING envs fonts lib man pyodbc.pyi sbin ssl x86_64-conda_cos6-linux-gnu
cmake conda-meta docs etc include libexec pkgs README share var x86_64-conda-linux-gnu
balter@exahead1:~$ find . -type d -name "condabin"
balter@exahead1:~$ conda activate
(base) balter@exahead1:~$
So,
- My path contains a directory that doesn't exist.
- I can run a command, e.g.
micromamba
, thatwhich
doesn't know the location of.
How does this work, and what is the purpose of ~/micromamba/condabin
?