Let ingestion script move existing compat layers instead of removing them #176
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When ingesting an updated compat layer, this adds a suffix to the existing one instead of removing them.
Example / test on the pilot repo with only
/cvmfs/pilot.eessi-hpc.org/versions/2023.06/compat/linux/x86_64
in place:Doing it once more with both
/cvmfs/pilot.eessi-hpc.org/versions/2023.06/compat/linux/x86_64
and/cvmfs/pilot.eessi-hpc.org/versions/2023.06/compat/linux/x86_64-001
already in place:This can be used as a first step towards making
x86_64
andaarch64
a variant symlink, allowing us to easily switch between compat layer versions (in that case the new one should also get a suffix when it's being ingested; that's not implemented yet). At the moment it doesn't use variant symlinks, nor does it change the path of a newly ingested compat layer, so it shouldn't change/break anything.