Items tasklist to go through for next Lmod RPM

[fgeorgatos]

This list looks long but they are all of them non-blockers, so the situation is quite good as of now.

• --version & --gitversion (or git TAG pointing thereof) SHOULD match the package name; fi. Update Lmod-illumina.spec #83
• SitePackage.lua could be a non-broken one :-) inspect that syslog entries work out of the box
  • fi. use https://github.com/TACC/Lmod/pull/273/files
  • also fix Current Lmod.spec overwrites existing /etc/site/lmod/SitePackage.lua, let's improve #84
• /usr/share/lmod/lmod/modulefiles/Core/settarg : This is a total MUST-have for developers
• Lmod/7.4.x RPMs should be explicit about their dependencies; also fix SitePackage.lua #81 : define in .spec file lua extensions as Bright Lmod RPM dependencies (what about repo?)
  • yum localinstall lua-{bit32-0.2,filesystem-1.6.3,posix-33.4.0}-1000_cm7.0.x86_64.rpm
  • ref. http://support.brightcomputing.com/illumina/
• validate against FindFirst (D) bug, ie. Is the default modulefile always the one with the highest prefix or what? TACC/Lmod#275
  • LMOD_TMOD_FIND_FIRST=true
  • Confirmed in: Is the default modulefile always the one with the highest prefix or what? TACC/Lmod#275 (comment)
• module unuse tab completion should work, too (it does work in manual Lmod delivery):
  • Hint it only searches existing loaded modules
• make use.own.eb be available per default, under /etc/site/module ?! (TBD)
• Perhaps define automagically EASYBUILD_MODULES_TOOL=Lmod ?! (TBD, default modulefile?)
• what if $MODULEPATH or $LMOD_SYSTEM_DEFAULT_MODULES need to be initialized externally to RPM files? how do this? (TBD)
• related to last one, which would be the right place for handling $LMOD* environment variables? (TBD)
• similarly, $USER_IS_ROOT probably should be external to the package (TBD)

and also:

• an empty $LD_LIBRARY_PATH should not trigger reinitialization of environment; ref. Issue45: avoid looking at $LD_LIBRARY_PATH; screen touches it #55
• Lmod_test_suite should provably be able to pass - automate any further testing via any of:
  • use shell-doctest
  • OR cram
  • OR bats
  • OR shtst
    ref. https://github.com/rtmclay/Lmod_test_suite
• if possible, avoid the BASH_ENV modifications - bad karma, that may conflict with other packages
• pass once more through the hoops of the checklist at Checklist for recent Lmod RPMs #70