This is why Spack was created:<p>> <i>Spack is a package management tool designed to support multiple versions and configurations of software on a wide variety of platforms and environments. It was designed for large supercomputing centers, where many users and application teams share common installations of software on clusters with exotic architectures, using libraries that do not have a standard ABI. Spack is non-destructive: installing a new version does not break existing installations, so many configurations can coexist on the same system.</i><p>* <a href="https://spack.readthedocs.io/en/latest/" rel="nofollow">https://spack.readthedocs.io/en/latest/</a><p>> <i>Spack is a package manager for supercomputers, Linux, and macOS. It makes installing scientific software easy. Spack isn’t tied to a particular language; you can build a software stack in Python or R, link to libraries written in C, C++, or Fortran, and easily swap compilers or target specific microarchitectures.</i><p>* <a href="https://spack.io" rel="nofollow">https://spack.io</a><p>Intro presentation from some HPC conferences:<p>* <a href="https://www.youtube.com/watch?v=edpgwyOD79E" rel="nofollow">https://www.youtube.com/watch?v=edpgwyOD79E</a><p>* <a href="https://www.youtube.com/watch?v=DhUVbroMLJY" rel="nofollow">https://www.youtube.com/watch?v=DhUVbroMLJY</a><p>Very similar to (home)brew, MacPorts, etc, with more of a focus on HPC so you can have multiple versions of a particular piece of software, made with different compiles and linked against different library version.