t: introduce WITH_BREAKING_CHANGES prerequisite

Earlier c5bc9a7f (Makefile: wire up build option for deprecated
features, 2025-01-22) made an unfortunate decision to introduce the
WITHOUT_BREAKING_CHANGES prerequisite to perform tests that ensure
the historical behaviour that may be different from what we will
have in the future.  It would inevitably invite double-negation when
we need to add tests to ensure the behaviour we want to have in the
future.

Introduce WITH_BREAKING_CHANGES prerequisite and replace the
existing uses of WITHOUT_BREAKING_CHANGES prerequisite.  To catch
any future topics that add more uses of WITHOUT_BREAKING_CHANGES,
mark it as a removed prerequisite.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Junio C Hamano
2025-03-11 14:25:02 -07:00
parent 1c24d55a2f
commit 926d18e58d
5 changed files with 15 additions and 10 deletions

View File

@@ -1862,8 +1862,13 @@ test_lazy_prereq CURL '
curl --version
'
test_lazy_prereq WITH_BREAKING_CHANGES '
test -n "$WITH_BREAKING_CHANGES"
'
test_lazy_prereq WITHOUT_BREAKING_CHANGES '
test -z "$WITH_BREAKING_CHANGES"
# Signal that this prereq should not be used.
exit 125
'
# SHA1 is a test if the hash algorithm in use is SHA-1. This is both for tests