Re: Using "module load" in a modulefile

[Dave B. <ba...@ho...>]

Leo:

One suggestion I might make is that you do something similar to how
we've done a few of our modules.

1.  In the module file proj1, do setenv SYNOPSYS_VER "1999.10", and then
just do module load Synopsys (i.e. don't specify a version here, use the
default one supplied by the .version file).
2.  Make your Synopsys/.version file look similar to this:
	#%Module1.0
	set ModulesVersion = "1999.05"
	if { [info exists env(SYNOPSYS_VER)] } {
	    set ModulesVersion = $env(SYNOPSYS_VER)
	}

When you do the above, the default module would be 1999.05 for everyone,
except those who override it with the env var SNYOPSYS_VER (either
manually 'cause they know what they're doing, or because proj1 does it
for them).

In theory (not able to test it, but should work), you then should be
able to module switch proj1 proj2, and it should 'do the right thing': 
unload proj1 (and the default version of Synopsys (provided by the
.version file) ) and load proj2.


Doing the above in your .version file is a slick way to allow
knowledgeable users (or developers) to test things before unleashing new
versions on the rest of the population.

Good luck.

Cheers,
Dave

-- 
Dave Barnett	Software Support Engineer	x1434
"If it's zero degrees outside today and it's supposed to be twice as
 cold tomorrow, how cold is it going to be?"
	- George Carlin