ACCESS-NRI Spack packages

This is a Spack package repository maintained by ACCESS-NRI for packages that are not available in the upstream Spack package repository. Where possible Spack package recipes (SPRs) written by ACCESS-NRI will be contributed to the upstream Spack packages repository.

The namespace of the ACCESS Spack package repository is access.nri.

How to utilise this package repository

If you want to build ACCESS models on Gadi, the How to use Spack on Gadi for building ACCESS models document may be more relevant than this document.

The instructions below will create an editable access-spack-packages repository.

Note

$SPACK_ROOT and $ACCESS_SPACK_PACKAGES_PATH are substituted in all paths to make these instructions installation independent.

If you are not using ACCESS-NRI's spack-config, a default installation of Spack will have a single package repository (builtin):

$ spack repo list
[+] builtin    v2.2    $SPACK_ROOT/../package_repos/fncqgg4/repos/spack_repo/builtin

And the following package is not available:

$ spack list libaccessom2
==> 0 packages

To use the SPRs in this repository, first check if your Spack instance already includes this repository (spack repo list). If not, then add it manually:

spack repo add https://github.com/ACCESS-NRI/access-spack-packages $ACCESS_SPACK_PACKAGES_PATH

and then confirm it has been added correctly:

$ spack repo list
[+] builtin       v2.2    $SPACK_ROOT/../package_repos/fncqgg4/repos/spack_repo/builtin
[+] access.nri    v2.0    $ACCESS_SPACK_PACKAGES_PATH/spack_repo/access/nri

Now, the libaccessom2 package should be available to install

$ spack list libaccessom2
libaccessom2
==> 1 packages

Spack does a shallow clone of the repositories. To restore the full functionality of the git repository, run: git -C $ACCESS_SPACK_PACKAGES_PATH fetch --unshallow . Now, it is possible to use an older version of the access-spack-packages repository by running git -C $ACCESS_SPACK_PACKAGES_PATH switch -c <NEW_BRANCH_NAME> <GIT_TAG>. However, please note that older versions of access-spack-packages may not be compatible with recent versions of Spack.

More information

• The Spack package repository that was used with pre-v1.0 Spack is available in the api-v1 branch

• For more information see the extensive spack documentation on how to utilise repository files.

• This repository utilizes automatic tagging on the default branch, upon merging, in the form YEAR.MONTH.00MINOR (for example, 2026.05.001). See the workflow file for more information.