Pirbo refresh scratch #358
Draft
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
Maybe I'm doing a mistake because I miss the motivation for having a multi step build in the first place: I don't see where files are generated in one step to be erased in a following one. In any case, generated images are actually smaller (!) than when / is recursively copied in a fresh image. And we take advantage of having the problematic environment variables unset (aka the compilation of 'opam-core' is fixed).
toots
force-pushed
the
pirbo-refresh-scratch
branch
4 times, most recently
from
a8d1c63 to
024963c
Compare
toots
force-pushed
the
pirbo-refresh-scratch
branch
from
024963c to
9b86ff5
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.
No description provided.