Force fallback for venus-protocol - #74
Open
RedSQL wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
1 participant
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.
Recent MR 43406 over at mesa broke building drivers that use venus as
venus-protocolis now not in-tree and is pulled as a subproject instead. This PR addsvenus-protocolas a forced fallback so meson pulls venus subproject and builds. I have built successfully with this applied.I am not entirely sure if this is the correct way to approach this, perhaps this should've been gated behind
c7919be1fa9d99a75eb6ec6042fdff6265fe55e5commit ancestor? Though forced fallbacks aren't gated behind in the first place, so perhaps we should be fine, maybe? Let me know if there is anything that needs changing! 🐸