|
From: R.K. O. Ph.D. <rk...@Ow...> - 2002-07-28 16:00:00
|
Hello All: If you've been looking at the CVS repository for modules ( http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/modules/modules/ ) you may have noticed that there are lots of changes being made for the upcoming 3.2 version. The prime one for me is deep modulefile directories, and I've had some success in making it happen. However, there are some little used features (to me) that are causing great difficulties, and I wanted to get a sense of what's being used out there. 1) Does anyone use the .modulerc files? To do things like module-version module-alias both of these commands rely on a shallow directory structure in their implementation. I have never used them for my own use, though, and can only see a number of limited ways where they may be useful. I could just assume that both are broken and re-code both into a workable form, but with slightly different semantics. 2) Caching for "module avail". I rarely enable it for my own systems, but I have maybe 50+ modulefiles on each. At one of the sites I had frequented, they had hundreds of modulefiles where each package had modulefiles for various versions, and they never removed anything no matter how old and crufty. I tended to not do "module avail" there because they just had too much garbage to wade through. (BTW - they used a serious old version, I used my own instead, but needed --disable-version-magic to read their .version files.) Your comments would be appreciated, R.K. +------------------+---------------------+ | R.K.Owen,PhD | rk...@ow... | | KooZ Software | Environment Modules | | NERSC/LBNL | rk...@ne... | +------------------+---------------------+ |
