Years ago I made a modification to the tcl module package that actually cached the full path to each modulefile loaded.  That way, when you unloaded, it didn't matter if the module was even in the modulepath anymore (which was a problem we kept running into).  I tried to donate it back to the community back then, but it was a real slow period in module interest and it never happened.  Adding this sort of functionality would solve your problem as well.


Andy


On 03/11/2012 02:50 PM, Hugh Macdonald wrote:
Hi again,

I thought I'd start a new thread for this one, as, while it's connected, it's a much more cut and dry question.


Can I, inside a module, specify which actual version has been loaded?

I plan on having the following files (arrows imply symlinks)

1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0 -> 1.0.5
1.1.1
1.1.2
1.1 -> 1.1.2
1 -> 1.1

So I can ask for 1.0 to be loaded, and it'll load 1.0.5, or ask for 1 to be loaded, and it'll load 1.1.2

However, consider the following situation:

module load MyPackage/1.1   # Loads 1.1.2
module list   # Will list MyPackage/1.1 rather than MyPackage 1.1.2
# MyPackage 1.1.3 is released, including re-linking 1.1 to 1.1.3
module unload MyPackage/1.1   # Will attempt to unload 1.1.3, which won't be in the paths, so it won't properly unload


Ideally, I'd love to know if there is a way inside, say, 1.1.2 to specify that it is actually 1.1.2 that has been loaded, and not whatever was requested in the 'module load' command.


Any ideas on this?

Cheers

Hugh
------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________ Modules-interest mailing list Modules-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/modules-interest