Our installed software is moving from /apps to CVMFS. As before, we DO NOT include these paths in your shell by default.
Until we have our own Stratum 0 repository, we are leveraging OASIS (the OSG Application Software Installation Service). It's a long path, but only has to be used once:
% module use /cvmfs/oasis.opensciencegrid.org/jlab/scicomp/sw/el9/modulefiles
Then you can see which modules are available. Omitting a specific module name will list all.
% module av
------- /cvmfs/oasis.opensciencegrid.org/jlab/scicomp/sw/el9/modulefiles -------
cernlib/2023 groovy/4.0.16 root/6.24.08-gcc11.3.1
gcc/11.4.0 julia/1.6.7 root/6.26.14-gcc11.3.1
gcc/12.2.0 julia/1.9.4 root/6.28.10-gcc11.3.1
gcc/12.3.0 pythia/6.416 root/6.30.02-gcc11.4.0
gcc/13.2.0 pythia/6.428
gradle/8.5 pythia/8.310
------------------------ /usr/share/Modules/modulefiles ------------------------
dot module-git module-info modules null use.own
Loading a module will update your environment by setting things like $PATH, $LD_LIBRARY_PATH, and $MANPATH. Using module show <name/version>
will list specifically what is modified.
% module use /cvmfs/oasis.opensciencegrid.org/jlab/scicomp/sw/el9/modulefiles
% module load gcc/13.2.0
% which gcc
/cvmfs/oasis.opensciencegrid.org/jlab/scicomp/sw/el9/gcc/13.2.0/bin/gcc
% gcc --version
gcc (GCC) 13.2.0
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Depending on the version of environment-modules that's installed, it sorts the versions differently. For example, using 'module load gcc' will load gcc/9.3.0 instead of gcc/10.2.0. So it's best to specify the version you want for consistent results.
You can request for new packages to be installed into CVMFS by submitting a ServiceNow incident.