|
From: David C. M. <dav...@ba...> - 2001-07-18 17:21:50
|
"R.K. Owen Ph.D." wrote: > > I like to group my modules into categories. For example, > browsers/netscape/4.61, browsers/netscape/6.0, browsers/opera/4.0, etc. > and what happens is that the .version files don't get read. Say > browsers/netscape/.version points to 4.61 which is totally ignored and > netscape/6.0 will be loaded if doing "module load browsers/netscape" > Glad to see that you are back working on modules again. We are a shop that uses "deep modulefile directories", and I will be very interested when you solved the deep .version files problem you have described above. It is the show stopper that is preventing our move to modules 3.x. >From a historical perspective modules 2.x supports deep modulefile directories. An unfortunate side effect of the subsequent development efforts for new modules functionality apparently broke that feature. Even if may folks do not use or appreciate the value of deep modulefile directories, modules operation should be consistent throughout - e.g. if 'module avail/load/unload' supports deep modulefile directories, then all aspects of that support (i.e. .version files) should follow. I would have thought that if these routines had been coded in a recursive style, then the operation of .version files would have never come up as an issue in the deeper directories. However, that is water over the dam..... Dave |
