Add --force-basename option #13
Open
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
When extracting multiple similar archives with only one top-level element, user usually wants to have them in a destination directory named after archive's name. Currently the first archive is extracted to a directory named after the single top-level element while other archives are extracted to directories named after archive's basename. The `--force-basename` option is forcing the latter behaviour for every archive. For example, let's say we have two archives, with only one top-level directory in them (called `var`): ``` $ ls BundleLogs*zip BundleLogs-1495008842230.zip BundleLogs-1495008843374.zip ``` When trying to unpack them at once: ``` $ unp --output /tmp/logs BundleLogs*zip ``` The default behaviour leaves us with: ``` $ ls /tmp/logs BundleLogs-1495008843374 var ``` Using `--force-basename` option: ``` $ unp --force-basename --output /tmp/logs_basename BundleLogs*zip ``` We get the following result: ``` $ ls /tmp/logs_basename BundleLogs-1495008842230 BundleLogs-1495008843374 ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When extracting multiple similar archives with only one top-level
element, user usually wants to have them in a destination directory
named after archive's name.
Currently the first archive is extracted to a directory named after
the single top-level element while other archives are extracted
to directories named after archive's basename.
The
--force-basenameoption is forcing the latter behaviour for everyarchive.
For example, let's say we have two archives, with only one top-level
directory in them (called
var):When trying to unpack them at once:
The default behaviour leaves us with:
Using
--force-basenameoption:We get the following result: