search

ACCESS-NRI / spack-config

Shared spack configuration
Apache License 2.0
1 stars 0 forks source link

Support multiple versions/targets of `spack` with differing configs #7

Closed CodeGat closed 10 months ago

CodeGat commented 10 months ago

Different versions of spack may require different versions/targets of spack_config.

Either:

harshula commented 10 months ago

Should we have symmetry with the spack instance? e.g.

$ git branch -r | grep releases\/
  origin/releases/v0.10
  origin/releases/v0.11
  origin/releases/v0.12
  origin/releases/v0.13
  origin/releases/v0.14
  origin/releases/v0.15
  origin/releases/v0.16
  origin/releases/v0.17
  origin/releases/v0.18
  origin/releases/v0.19
  origin/releases/v0.20
  origin/releases/v0.21

i.e. Have a v0.20, v0.21, ... branches?

Or do we want transparency and have versioned config directories in main branch? I've been flip-flopping between these two options since last week.

CodeGat commented 10 months ago

I'm really not sure...I do like the idea of versioned config directories. Seems a bit simpler to maintain than having to modify each branch whenever something needs to be modified.

harshula commented 10 months ago

Fixed by PR https://github.com/ACCESS-NRI/spack_config/pull/10