Recently I implemented various boolean configs which control how to behave when
there is a share-safe mismatch between source and share repository. Mismatch
means that source supports share-safe where as share does not or vice versa.
However, while discussion and documentation we realized that it's too
complicated and there are some combinations of values which makes no sense.
We decided to introduce a config option with 4 possible values which
makes controlling and understanding things easier.
The config option share.safe-mismatch.source-{not-}safe can have
following 4 values:
- abort (default): error out if there is mismatch
- allow: allow to work with respecting share source configuration
- {up|down}grade-abort: try to {up|down}grade, if it fails, abort
- {up|down}grade-allow: try to {up|down}grade, if it fails, continue in allow
mode
I am not sure if I can explain 3 config options which I deleted right now in
just 5 lines which is a sign of how complex they became.
No test changes demonstrate that functionality is same, only names have changed.
Unrelated to this patch, but maybe we should interpolate requirementsmod.SHARESAFE_REQUIREMENT so this doesn't get forgotten about when renaming the requirement?