David C. Mores (dav...@ba...) wrote:
> Your can use the .version or .modulerc to control which
> version of an application is going to be the default on
> a particular platform with something like this:
> [snip]
Great example, David.
I just wanted to comment on your last paragraph:
> This is an arrangement we have been using successfully for
> the past 10 years with Modules version 2.2b. Version 3.x
> still has problems with more than two directory levels.
Version 3.1.6 of modules is likely to be the last version
in the 3.1.x branch, and this issue won't be addressed there.
The code base has been undergoing a fairly significant rewrite
in the 3.2 branch, with the "greater than 2 levels" issue one
of the things being dealt with.
One group in our company is still on modules 2.2b as well,
although I moved my group over to 3.1.x some time ago. I'm
looking forward to the >2 levels as well so we can all be on
the same version here.
I must say that I've been delighted with the fact that all of
the Tcl I've added to the modulefiles to implement various
features has been compatible between both versions of modules.
Just FYI.
Regards,
- Leo Butler
|