Changes between Version 44 and Version 45 of HPC_deploy

Timestamp:

2017-06-15T19:13:19+02:00 (8 years ago)

Author:

Pieter Neerincx

Comment:

--

HPC_deploy

@@ -323 +323 @@
 A: When you have an !EasyConfig of type {{{easyblock = 'Bundle'}}} with a long list of extra  modules, packages, etc. for a language like Perl, Python, R, etc. and your install failed partially it ain't fun to start all over from scratch. 
 You can resume the install after fixing the issue when
-* Your config specifies the extension defaultclass (= the !EasyBlock) using {{{exts_defaultclass = 'someEasyBlock'}}} 
-* and the extension filter (= command to test whether installation of the extension succeeded) using {{{exts_filter = ("someCommand", "")}}}
-* and when you've added the path where the additional modules/packages will be installed to the language specific environment variable that is used to search for extras - {{{PERL5LIB}}} for Perl, {{{PYTHONPATH}}} for Python, {{{R_LIBS}}} for R, etc.
+* your !EasyConfig specifies
+  * the extension defaultclass (= the !EasyBlock) using 
+    {{{
+exts_defaultclass = 'someEasyBlock'
+    }}} 
+  * and the extension filter (= command to test whether installation of the extension succeeded) using 
+    {{{
+exts_filter = ("someCommand", "")
+    }}}
+  * and adds the path where the additional modules/packages will be installed to the language specific environment variable that is used to search for extras - {{{PERL5LIB}}} for Perl, {{{PYTHONPATH}}} for Python, {{{R_LIBS}}} for R, etc. using 
+    {{{
+modextrapaths = {'ENVVAR': ['path', 'another/path']}
+    }}}
 * and when you use the {{{--skip}}} and {{{--resume}}} commandline options for the {{{eb}}} command - e.g. 
   {{{