miniforge VS hunter

Nope they don't use venv for any of the oobabooga# variants nor is it recommended for the git version. I'm using https://github.com/conda-forge/miniforge#mambaforge-pypy3 (better version of the recommended conda) for the git variant. The oobabooga* variant uses micro/miniconda (I suck with names) which you can easily drop into with cmd_?something? and does it all internally. Like whoever built that whole environment setup for the _windows/linux/mac did a great job.

wget https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-Linux-aarch64.sh .

Mambaforge!

Just to further clarify: you don't need mamba to avoid the Anaconda distribution. The place you get mambaforge also supplies (and originally supplied) miniforge, which is miniconda with conda-forge set as the default channel. All the *forge installers do in this regard is automatically set conda-forge as the default (and only) channel, which is something one can do manually with miniconda.

I'd recommend using miniforge if you're comfortable with CLIs, otherwise https://www.anaconda.com/.

Tip 1: To use less of your Codespaces resources start with a smaller image like Miniconda or Miniforge and install only what you need.

miniforge, no need to deal with conda environments anymore. https://github.com/conda-forge/miniforge

You forgot https://github.com/cpp-pm/hunter, which actually has more packages than Conan, but less than vcpkg.

Use Hunter for dependency management

https://github.com/cpp-pm/hunter

There is a bit of a learning curve, but it's the only dependency manager that does things right (all from within CMake)

Hunter package manager is missing. Or is it a part of "managing dependencies manually?"

Ahh yep fair enough. I've used hunter for that previously but conan looks really good.