Use proper index versioning for backwards compatibility #975
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fabien-Chouteau
approved these changes
Apr 8, 2022
src/alire/alire-toml_index.adb
Outdated
|
|
||
| procedure Compare_Branches (Local : String) is | ||
| Local_Kind : constant String := AAA.Strings.Head (Local, "-"); | ||
| -- Local_Version : constant Semantic_Versioning.Version := |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently we are emitting a hard error if either the index branch or version do not match.
With this PR, Alire knows the range of compatible versions (assuming we add features without breaking back compatibility), so now a warning is emitted for old compatible versions and mismatched branches. The error is only produced by a too old index version.
This should result in simpler switching between stable/devel versions, and also be less painful for people with private indexes whenever we add some new feature that does not break compatibility, as they're not forced to update their version on the spot.