Hi,

Because of interoperability of software, I see an increasing need to fix 
software versions beyond what is included in the actual toolchains.  I am 
discussing standard dependencies, like jpeg libraries, HDF5, netcdf, curl.  So, 
unless there is strong reasons (e.g. bugs), packages build with a certain 
toolchain (e.g. foss/2017a) should use a “preferred version” for standard 
dependencies.  Using the latest and greatest, which is what I did some time ago 
has downsides in the form of module load conflicts.

The question is how would one administer this (selection of version(s), 
communication between contributors, …), without driving the administrative 
burden even higher.  I like to put this for discussion among the regular 
contributors.

Best wishes
   Joachim

Reply via email to