[Modules] difference on MANPATH for tcsh between v3.2 vs v5.4

[Laurent B. <lau...@ea...>]

Hello,

Recently, I found that a simple < man ls > was no more working in my tcsh unix environment. Which is a bit surprising ! A < man > command reporting < No manual entry for ls > is quite odd on a Unix system !

After a bit of investigation, I found that my MANPATH variable was defined to < /tool/platform/lsf/8.0/man > without any mention to < /usr/share/man > or other regular unix man page dir. Weird ! But it explains why < man ls > was not working !

When using 5.4.0 version of Modules, here what I see, starting from a fresh terminal :


  1.  Before any module load, MANPATH variable is unset
  2.  < man ls > is working fine
  3.  Loading a module that has a < append-path > on MANPATH
  4.  < man ls > is no more working
  5.  MANPATH value is < /tool/platform/lsf/8.0/man >

But when using a very old version of Modules, precisely 3.2.10 (from 2012 !!!!), I see :


  1.  Before any module load, MANPATH variable is unset
  2.  < man ls > is working fine
  3.  Loading a module that has a < append-path > on MANPATH
  4.  < man ls > is still working fine
  5.  MANPATH value is < /tool/platform/lsf/8.0/man:/usr/share/man:/usr/local/share/man >

So, from my point of view, there is a regression on behavior of Modules when switching from 3.2 to 5.4

Could I have your opinions on this topic ? Is it a bug or a feature ?

Best regards,
Laurent.