tar 1.14 compatibility (Tiger) - #1
Open
cellularmitosis wants to merge 17 commits into
Open
Conversation
Credits @RJVB
|
@cellularmitosis That code was added ages ago: macports@db32814 |
|
@cellularmitosis Where are we on this? |
|
@cellularmitosis If you could ensure that 2.11.5 actually builds and works on Tiger, that will be great, since currently that is totally untested. |
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
2 participants
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.
Between tar 1.14 and 1.15,
--strip-pathwas renamed to--strip-components.Tiger shipped with 1.14, and leopard shipped with 1.15.1.
MacPorts currently uses
--strip-components, which causes an error on Tiger.This PR invoke
tar --versionto detect which flag should be used.DO NOT MERGE YET I have not figured out how to test this yet. When I ran
sudo port syncafter building macports-base from source (without the patch), for some reason it didn't trigger the error, so now I'm not sure how to trigger that code path.