"R.K. Owen Ph.D." <rk...@Ow...> writes:
> Hello, I have a couple of questions, because of all the respondents
> you may be the most affected by the semantic changes.
>
> So for the example below you have the bar module load foo with:
> module load foo/bar
>
> and that the .modulerc file exists at the modulefile "root"?
No, the modulerc is at $MODULEPATH/foo/.modulerc, a separate one for
each package:
$MODULEPATH/
foo/
.modulerc
4.1.1
5.2
5.2.1
6.2
otherpackage/
.modulerc
1.0
2.0
yapackage/
.modulerc
1.5
1.6
> If so, then the proposed new semantics would be that the .modulerc
> file exists in the ./foo directory and would likely be:
>
> #%Module1.0
>
> module-version 4.1.1 obsolete_deleted_May2000
> module-version 5.2 bar # this is the version to be used with package bar
> module-version /5.2.1 OBSOLETE-1020718c
> module-version /6.2 default
>
> where only "versions" are given with an optional prepended '/'
> and you continue to use "module load foo/bar" to load foo/5.2 .
>
> This .modulerc set-up would backwardly compatible too.
OK, so since we already have .modulerc inside foo all we'd need to do
is change the version numbers from foo/4.1.1 to 4.1.1 right? I will do
some tests with the current CVS version to see how it behaves on our
current setup and with this change.
--
Istvan
|