allow mirror url to be set in project.json file

[cyrush]

it makes life easier to have an option to store it here, vs always pass on the command line

[adrienbernede]

@cyrush what about creating a mirrors.yaml file in the desired spack_configs/<sys_type> and modify uberenv so that it copies it as well? (Just tested, it works fine.)

Note: with environments this won't be necessary anymore (#18).

[cyrush]

that does seem like a good option, but I am using the same mirror across configs,
creating lots of mirror.yaml files is harder to manage vs setting in one place.

[white238]

We really need to move to environments. They solve a lot of these problems.

[adrienbernede]

We could apply the same logic as for "config.yaml": copy the top level one, and if present override with the one in the spack_config/<arch> dir.

[adrienbernede]

@white238 agreed. PR ready, and demo in Umpire OK ;)

[cyrush]

in that we can cascade them (nest scopes depending on platform)?

[adrienbernede]

in that we can cascade them (nest scopes depending on platform)?

Sorry, not sure what you are asking.

[cyrush]

My question was for @white238, so to how env's help.
I think env's help b/c we can have overall settings (like mirror settings) and then include another env file with packages and compilers?

@adrienbernede can you point me to the umpire stuff?

Already down a rabbit hole for a spack update, I am planning on doing an uberenv update as well.
I have env files I can test.

[adrienbernede]

Umpire with "Environment based version of Uberenv":
LLNL/Umpire#481

[white238]

Just that we keep running into problems that environments solve. I thought you could add mirrors to environment files but i can't seem to find it in their documentation.

[adrienbernede]

@white238 You just can.

[adrienbernede]

Syntax is just like if you included the mirrors.yaml file (the same way as for packages.yaml etc.)