build_source_code.md: Update from Spack v0.22 to shared Spack v1.1

[harshula]

Objective

Planned changes to the document:

• Spack v0.22 to shared Spack v1.1
• ACCESS-ESM1.5 to ACCESS-OM3
• Managed environment to indepedent environment
• Improve brevity

[github-actions]

PR Preview
🚀 Preview of PR head commit 2622264 deployed to https://docs.access-hive.org.au/pr-previews/1154
2026-07-03 16:47 AEST
Preview generated through the Deploy to GitHub Pages workflow run 28643610391.

[harshula]

Hi @atteggiani , Since all the development work is now focussed on ESM1.6, should we update this document to use ACCESS-ESM1.6 as the example instead of ACCESS-ESM1.5?

[atteggiani]

Hi @atteggiani , Since all the development work is now focussed on ESM1.6, should we update this document to use ACCESS-ESM1.6 as the example instead of ACCESS-ESM1.5?

Yes, I think it makes sense as it will be more relevant for readers.

[harshula]

@chrisb13 noted, "I gather this last doc will be updated to use independent env's right? If that is some time away, I think a warning that it's different to the set up spack page would be a kindness for less familiar users."

[harshula]

Hi @chrisb13 , I've made the "Spack v0.22 to shared Spack v1.1", do you want to start the "ACCESS-ESM1.5 to ACCESS-OM3" and "Managed environment to indepedent environment"?

Hi @atteggiani , What's your preferred way to proceed?

[atteggiani]

I'm happy for changes to be added directly within this PR, I think would be the quickest solution

[chrisb13]

do you want to start the "ACCESS-ESM1.5 to ACCESS-OM3" and "Managed environment to indepedent environment"?

Not sure what you are asking for here @harshula? Do you mean adding some kind of warning regarding this concern?

[harshula]

Had a chat with @chrisb13 yesterday to clarify his next steps.

[anton-seaice]

I assum the access-spack-packages version isn't controlled by the user anymore ?

(i.e. this section can be removed ?)

[harshula]

By default access-spack-packages is managed by the shared Spack instance and is not editable. However, when a user needs to edit access-spack-packages, there are these instructions https://github.com/ACCESS-NRI/access-spack-packages and https://github.com/ACCESS-NRI/spack-config#gadi-advanced-user-optional .

Thanks for pointing it out, I'll correct it.

[harshula]

Updated text: https://access-hive-docs--1154.org.readthedocs.build/models/build_a_model/build_source_code/#set-access-spack-packages-version

[ashjbarnes]

Thanks Spack team! @anton-seaice pointed me here after I got a bit lost trying to follow the older instructions despite being on 1.1. Can confirm that these updated instructions worked for me once @CodeGat and @anton-seaice suggested I use these additional advanced instructions

https://github.com/ACCESS-NRI/spack-config#gadi-advanced-user-optional

Since I'm developing with new code (access ESM3) I needed access to the latest spack packages. Perhaps this could be mentioned after the concretize step in the new instructions to point people in the right direction if they hit a "package doesn't exist" error?