From 0bd838bd1127da8d5b38ded85460e6081d236a80 Mon Sep 17 00:00:00 2001 From: Matthew Scott Krafczyk Date: Thu, 14 Sep 2017 20:49:25 -0500 Subject: Remove echo statements from setup-env.sh setup-env.sh adds the 'module' command to the user's environment if it is not defined and if there is a Spack installation of environment-modules available. This commit updates that logic to perform these checks and updates quietly. --- share/spack/setup-env.sh | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/share/spack/setup-env.sh b/share/spack/setup-env.sh index 74820ecb93..4de530beba 100755 --- a/share/spack/setup-env.sh +++ b/share/spack/setup-env.sh @@ -230,18 +230,7 @@ if [ "${need_module}" = "yes" ]; then export MODULE_PREFIX=${module_prefix} _spack_pathadd PATH "${MODULE_PREFIX}/Modules/bin" module() { eval `${MODULE_PREFIX}/Modules/bin/modulecmd ${SPACK_SHELL} $*`; } - echo "INFO: Using spack managed module system." - else - echo "WARNING: A method for managing modules does not currently exist." - echo "" - echo "To resolve this you may either:" - echo "1. Allow spack to handle this by running 'spack bootstrap'" - echo " and sourcing this script again." - echo "2. Install and activate a supported module managment engine manually" - echo " Supported engines include: environment-modules and lmod" fi; -else - echo "INFO: Using system available module system." fi; # -- cgit v1.2.3-70-g09d2