Spack packages built with different specs have the same modulefile name #157
Description
@chrisb13 reported the following:
ACCESS-NRI/ACCESS-OM2#82 (comment)
@anton-seaice & @dougiesquire noticed that module load would pick the wrong MOM5 Spack package. It looks like we need to make the modulefile names unique again.
Here's an example of a name collision:
$ find [...]/prerelease/apps/spack/0.22/release/modules/ -iname '2024.08.23'
[...]/prerelease/apps/spack/0.22/release/modules/linux-rocky8-x86_64/mom5/2024.08.23
[...]/prerelease/apps/spack/0.22/release/modules/linux-rocky8-x86_64_v4/mom5/2024.08.23
The default Spack configuration appends the Spack hash to the modulefile name.