Hi Jens,
On 25/07/2012 14:10, Jens Timmerman wrote:
> But this would create to much clutter of 'fake/dummy' modules,
> so maybe replacing osdependencies with a 'prerequisites_commands', which
> contains a list of commands that shouldn't fail for this module to
> actually build would be a better option?
To prevent clutter, you could always have an "osdependencies" modulefile
which modifies MODULEPATH and brings in all that cruft. That still allows
you to a) override default tcsh with a custom build one when in need,
b) reduce dependencies on OS repositories and distro specific mechanisms
c) actually report problems when there are exact version dependencies
(otherwise a default yum/repo update can break a working HPC application).
What do you think?
--
echo "sysadmin know better bash than english" | sed s/min/mins/ \
| sed 's/better bash/bash better/' # Yelling in a CERN forum
