Add (Mini/Mamba)forge

[bollwyvl]

Related

• one approach to Setup-miniforge #76

Code Changes

• download-miniforge.ts
  • uses GitHub API to fetch releases (if version is not specified)... am trying to properly cache these, but i think there's some cache locality stuff
• removes some dead code
• tweaks provider logging to avoid constructions like Can we use use conda create?
• conda.ts
• if use-mamba and mamba-in-installer is specified, will try to use mamba earlier in the process, but also catches things like conda init which aren't supported by the mamba CLI yet
• installer/index.ts
  • now accepts (and can update) dynamic options, so that it can detect an installed mamba
• base-tools/index.ts
  • splits up tool specs and post-install
• upgrade-mamba.ts
  • can no-up the upgrading, but we will still want the mamba bash wrapper on windows without starting the solver)
• tests
  • adds workflow with a shotgun of different options to test out versions, interplay with other stuff

User-facing changes

• adds miniforge-variant, miniforge-version, to specify a Miniforge product
• adds mamba-in-installer and use-mamba to fine-tune use of Mambaforge
• updates the README, with some cross-links between mamba, custom installer, and this new provider

Backwards-incompatible changes

N/A

Follow-on

• with these changes, we're ready for micromamba (Micromamba based setup? #75), but:
  • the mamba CLI doesn't yet appear to support init for shell integration...
    • perhaps we can hot-install micromamba into the bundled miniconda bin or Scripts or condabin or something?
• while our list of inputs (and therefore our README) is getting rather long, I think from a maintenance perspective, keeping one action running that can do all the things is probably useful vs splitting effort (especially now that we've [do not merge] major refactor of downloads, environment creation #107-ed ourselves to where we are now)
  • perhaps we should consider doing a real docs site, potentially with a little "wizard" for building up a workflow
  • or, start using the GitHub wiki or discussions

[bollwyvl]

Hooray 💚 !

[goanpeca]

Thanks for working on this @bollwyvl, this is awesome :)

[jaimergp]

Can this be checked programmatically? Once installed one can check for mamba or mamba.bat in $PREFIX/condabin and determine it without user intervention, I think.

[bollwyvl]

hmmm... it's probably worth a look...

[goanpeca]

perhaps we should consider doing a real docs site, potentially with a little "wizard" for building up a workflow

Absolutely, I think we are big enough that we can have dedicated docs :) will set something with githubpages and myst :)

[bollwyvl]

Ok, so ab60b01 is back to 🟢 and 4651cc0 is mostly cosmetic... thanks @jaimergp for pushing to remove the manual thing: doing the detection uncovered a number of future bugs (e.g. adding that bash wrapper on windows).

example-10.yml is getting pretty hairy at this point, but I think has proven out a lot of cases (e.g. mamba in the installer upgrading to a specific mamba). I'd better stop tinkering with it.

Let's definitely squash merge this one :P

[jaimergp]

Nice!

adding that bash wrapper on windows

Hopefully this is addressed at the mamba level at some point (them providing a shell command like conda does)

[bollwyvl]

Nice! adding that bash wrapper on windows Hopefully this is addressed at the mamba level at some point (them providing a shell command like conda does)

Indeed. Guess we should issue? I'm a little mamba-ed out right now. God help zsh/fish windows users... But I could see xonsh, frankly... P-strings are awesome for windows "specialness".

[goanpeca]

Another awesome piece of work @bollwyvl :) 🥳

Thanks!