Install packages from dependency list as part of dev environment #10003
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.
The problem I'm trying to solve is related to #9787: We need a new native dependency
clangin the development Docker container, to be able to build native Ruby bindings to Rust code (because one new library relies on native Rust, and in the future there will be at least one more such library).This means that in its current state, we'd have to tell everyone on the whole team as well as external contributors to rebuild their Docker containers. This can take time and be costly for such a "simple" thing as adding one Debian dependency.
So my idea is to run the install step as part of the new
environmentbase container. If there is a more elegant way to achieve the same goal, please feel free to suggest that instead.