Begin bootstrapping of tricorders #5
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
leostera
force-pushed
the
feat/bootstrap
branch
from
38d9076
to
cba4067
Compare
leostera
force-pushed
the
feat/bootstrap
branch
from
cba4067
to
700b812
Compare
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.
Since the Mark I we've had the problem of bootstrapping of tricorders. In the Mark I we dealt with this by vendoring every dependency to avoid the resolution process. In the Mark II the resolution process is very different, so we need to come up with a new approach.
In this PR we work to make any tricorder bootstrappable by building them in a way that allows the least amount of incrementality (and thus the least amount of signature generation), while still allowing us to add incremental build support to them once they are built.