We have a guide for this written by Adam Stewart, probably our most prolific (package) contributor: * https://spack.readthedocs.io/en/latest/replace_conda_home

We have a guide for this written by Adam Stewart, probably our most prolific (package) contributor: * https://spack.readthedocs.io/en/latest/replace_conda_homebrew.html https://spack.readthedocs.io/en/latest/replace_conda_homebre... The thing you'll likely notice most about Spack vs. conda/mamba/rattler(?) is that it lets you pick your versions and options much more fluidly, and it'll build you a package from source if there's no binary for it. Spack is much more seamless for integrating binary installations with source builds. `conda-build` is a whole other tool outside the normal user workflow. Spack has over 7,000 packages at this point, so I don't think the lack of packages is going to hurt too much. We don't offer nearly as many public binaries yet, though, so the source builds may make the UX more painful, depending on what you're trying to do.