Essentially, we will need an overarching access-om3 SBD. This will be used to version the entirety of an access-om3 deployment release, including not only the access-om3 package, but the dependencies, the versions of spack-{packages,config} and the spack.yaml itself. This is similar to https://github.com/ACCESS-NRI/access-om2.
Currently we are leaning towards having the naming scheme as follows:
See https://github.com/ACCESS-NRI/ACCESS-OM3/issues/3#issuecomment-2044222491
Essentially, we will need an overarching
access-om3
SBD. This will be used to version the entirety of anaccess-om3
deployment release, including not only theaccess-om3
package, but the dependencies, the versions ofspack-{packages,config}
and thespack.yaml
itself. This is similar to https://github.com/ACCESS-NRI/access-om2.Currently we are leaning towards having the naming scheme as follows:
access-om3-virtual
access-om3
References ACCESS-NRI/ACCESS-OM3#3 References ACCESS-NRI/ACCESS-OM3#2