38,760
edits
Accessing CVMFS/fr: Difference between revisions
Updating to match new version of source page
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 194: | Line 194: | ||
==== <tt>RSNT_LOCAL_MODULEPATHS</tt> ==== | ==== <tt>RSNT_LOCAL_MODULEPATHS</tt> ==== | ||
This environment variable allows to define locations for local module trees, which will be automatically mesh into our central tree. To use it, define | This environment variable allows to define locations for local module trees, which will be automatically mesh into our central tree. To use it, define | ||
{{Command|export RSNT_LOCAL_MODULEPATHS=/opt/software/easybuild/modules}} | {{Command|export RSNT_LOCAL_MODULEPATHS{{=}}/opt/software/easybuild/modules}} | ||
and then install your EasyBuild recipe using | and then install your EasyBuild recipe using | ||
{{Command|eb --installpath /opt/software/easybuild <your recipe>.eb}} | {{Command|eb --installpath /opt/software/easybuild <your recipe>.eb}} | ||
This will use our custom module naming scheme to install your recipe locally, and it will be picked up by the module hierarchy. For example, if this recipe was using the <tt>iompi,2018.3</tt> toolchain, the module will become available after loading the <tt>intel/2018.3</tt> and the <tt>openmpi/3.1.2</tt> modules. | This will use our custom module naming scheme to install your recipe locally, and it will be picked up by the module hierarchy. For example, if this recipe was using the <tt>iompi,2018.3</tt> toolchain, the module will become available after loading the <tt>intel/2018.3</tt> and the <tt>openmpi/3.1.2</tt> modules. | ||
==== <tt>LMOD_SYSTEM_DEFAULT_MODULES</tt> ==== | ==== <tt>LMOD_SYSTEM_DEFAULT_MODULES</tt> ==== | ||