RE: [easybuild] MODULEPATH issue when supporting intel and intelcuda toolchain concurrently

We have used a toolchain-based naming scheme in the past and moved away from it because it was too complicated for users (too many levels in the hierarchy and the naming was very non-intuitive. On 3 Mar 2017 6:18 pm, "Siddiqui, Shahzeb" wrote: > Hello, > > > >

RE: [easybuild] MODULEPATH issue when supporting intel and intelcuda toolchain concurrently

Hello, Specifically for Intel I think for HMNS treat icc and ifort as packages and only toolchain have MODULEPATH The solution I think could be. Remove from icc and ifort module the modulepath for Compiler/intel Rather have iccifort module have a modulePath for iccifort When loading icc or

Re: [easybuild] Extended package documentation

On 02/15/17 09:20, Ward Poelmans wrote: > On 14-02-17 20:08, Kenneth Hoste wrote: >> >> I feel this sort of terse key/value style could be useful, but only for >> single-line info (e.g. homepage, contact, etc.). I (personally) totally agree with that. I have always considered 'module whatis' to