Hi Ken, all, On Sep 25, 2015, at 7:53 AM, Kenneth Hoste <[email protected]> wrote: > When stuff is hardcoded in easyblocks, it's mostly because of laziness that > there's no easyconfig parameter for it yet to turn it off...
IMHO, there is another view to this, not attributing it so much to human laziness: * we will never know (in advance) all the potential build parameters which might ever be needed to steer builds (fi. think of CUDA), therefor easyconfigs and (non-generic) easyblocks should be more tightly integrated and dynamically configurable. * Doing so, would prevent compatibility issues we currently face with old/new easyblocks. It shouldn't be like “human makes a choice” if easyconfig or easyblock is the right place, this kind of decision making should simply not exist! Your thoughts on this? Does anyone have an approach which does feel “just right”? Fotis -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # signal detected in a CERN forum
