Info on /home/easybuild/ being deprecated

uit-no · Jun 14, 2017 · d49fcd9 · d49fcd9
1 parent 27b6dde
commit d49fcd9
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/news/new_sw.rst b/news/new_sw.rst
@@ -59,8 +59,8 @@ Lmod allows a user to save a bundle of modules as a collection using ``module sa
 With a new module scheme came a different system MODULEPATH. For this reason, if you have some module collections saved, you will experience the following warning: "Lmod Warning:  The system MODULEPATH has changed: please rebuild your saved collection."
 To solve this you need to remove your old collections and create them again. We apologize for the inconvenience.
 
-If you are already using "mod_setup.sh"
-----------------------------------------
-If you have already started using the new modules by loading the "notur" module and sourcing "mod_setup.sh", simply remove these two steps and continue working as normal. We kept this option working for now to reduce the number of potentially crashing jobs, but we plan to remove it in the near future, so we recommend removing those lines from any new jobs you launch. You do not need the module "varset" any more, StdEnv has taken over its functionality. If the only reason you were using the "notur" module was to access the newer installations, you do not need it either. If you were using the "notur" module to run ADF or other software, then you still need to continue using it.
+If you are already using "mod_setup.sh" or "/home/easybuild/"
+------------------------------------------------------------
+If you have already started using the new modules by loading the "notur" module and sourcing "mod_setup.sh", simply remove these two steps and continue working as normal. The same goes for any references to /home/easybuild/. We kept these options working for now to reduce the number of potentially crashing jobs, but we plan to remove them in the near future, so we recommend removing those lines from any new jobs you launch. You do not need the module "varset" any more, StdEnv has taken over its functionality. If the only reason you were using the "notur" module was to access the newer installations, you do not need it either. If you were using the "notur" module to run ADF or other software, then you still need to continue using it.
 
 For information about how to reach the "new" packages, before we make this scheme default, see in the software section :ref:`new_scheme`.