Allow customization of the --build flag #594
Closed
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
This was referenced Nov 23, 2023
|
Hi @ssrobins - thanks for your contribution. We have just added a more generic We are actively avoiding to have specific flags mapped to specific arguments - and this is meant as the main point for additional customization. If it's not enough to satisfy your use case, please let us know! |
|
Makes sense, thanks! #612 works fantastically! |
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.
Right now, it's hardcoded to
--build=missing, but I'd like to be able to override that to pass--build=neverin continuous integration to enforce that all packages much have a binary. I generalized it so you could also pass a list of any--buildparameters to address other use cases folks may have.