Hello Todd, Samuel, In fact, it should be highlighted that -thanks to EasyBuild automation- this problem of “remembering the dependencies” practically does not exist since EB automatically inserts the correct bits and pieces in place. (inspect a modulefile, say, of PETSc and you will get the idea).
In summary, users need not remember any deps, it is just the build-provider who needs to be honest/precise about what are his intended deps. (to be fair: this battlefront is not over, since it’s more art than science about which deps come from OS/rpms and which ones are provided via other modules). F. On Jul 7, 2015, at 12:13 AM, Christopher Samuel <[email protected]> wrote: > On 04/07/15 09:42, Todd Gamblin wrote: > >> However, I am sick of having to load particular modules to run particular >> programs. If the program doesn't run when you invoke it, regardless of >> the environment, I think it's broken. Why do you expect the user to >> remember whether it was linked with OpenMPI or mvapich, and load the right >> one? > > We're not using EB (yet), but we try and ensure that our modules load > any dependencies needed that are not already loaded; if a program won't > run because we've missed something then that's a problem we need to fix. -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # signal detected in a CERN forum
