Remove "Compatibility" field from package card. #154
Merged
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
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.
This PR is in response to microsoft/vcpkg#37493
The "Compatibility" field in the package card:
Is currently based on whatever is in
ci.baseline.txt. It assumes the package is compatible with every triplet combination not listed inci.baseline.txt. This is inaccurate sinceci.baseline.txtasserts non-compatibility. It cannot be used to assert compatibility.Rather than trying a more complicated approach that maps the supports expression to triplets, I opted for removing the Compatibility field all together. The real fix is to use our latest ci run to report actual results. I will do this work on a different PR.