Workaround 2Gib file size limit by using compression and split
#36
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
|
Example here: https://github.com/SohamG/guix-installer/releases/ |
|
I'll go ahead and add a check to only split if its bigger than 2GiB |
|
Please squash when(if) merging. |
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.
Work around 2Gib release file limit as follows:
splitcommand, make multiple files. Add all files to release.In case of 2, user would have to cat all the files in order to a single targz before extracting. We can provide a shell script for this.
A longer term solution is to host the ISO on some cloud object storage.
Resolve #35