Repository navigation
Conversation
This file contains hidden or 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.
wimlib-imagex split currently applies a single size limit to every part, which makes it impossible to span a WIM across media with unequal capacities.
Concrete case: a Windows 11 install.wim (~7400 MiB) that has to fit on two 4.7 GB DVDs, where the first disc also carries the boot files. The first part must stay under ~3467 MiB while the second one takes whatever is left. With
wimlib-imagex split install.wim install.swm 3467, three parts come out, because every part is capped at 3467 MiB: ceil(7409 / 3467) = 3.Changes:
3467,rest,3467,*(first part <= 3467 MiB, second part takes the rest) ,3467,1350,2700or3467,1350(the last value is repeated for any further parts). A single number behaves exactly as before, andrest/*means "unlimited".