| Maybe I should clarify: > it basically boils down to removing that directory + the environment module file that EasyBuild generated for it Another important thing is knowing what depends on that package (so you don't remove something else's dependency). This is something that EB doesn't track after installation time. > EasyBuild can install "binary packages" What I meant here is that EB has no binary packaging system of its own. It has no binary package format, no signing, no way to take an installation and bundle it up into a file that can be installed (potentially in a different location) on another system. Spack, Nix, and Guix all have systems for creating and (re)installing binary substitutes for source builds (we call them build caches). EB can install someone else's binary package/distribution (we can too FWIW), but it can't create its own. > But maybe you're referring to installing software in a shared filesystem (NFS, usually something like /apps). Yes -- specifically that, with environment modules. Spack installations similarly all go in their own directories, but you can compose them in many different ways with environments and views. e.g., you can: - Create a symlink tree of many packages together in a common prefix (a view)
- "project" package installations into different directory layouts with symlinks, hardlinks, or relocated copies
See https://spack.readthedocs.io/en/latest/environments.html#vie...And you don't have to load packages one by one with modules. You can avoid modules entirely with `spack load` or use `spack env activate` to put everything in an env into your `PATH` (and other env vars). |