-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expand .xip on the destination volume #178
Comments
@juanjonol absolutely accept a PR for this. Did something similar with Xcode.app - if you could follow the similar pattern that would be 💯 https://github.com/RobotsAndPencils/XcodesApp/pull/155/files |
Instead of expanding XIPs on its current directory, a temporal directory is used. The main advantage of this approach is that, because the temporal directory is created on the same volume where Xcode will be installed, the installation is vastly improved if the XIP is on a different volume. - https://nshipster.com/temporary-files/ - The implementation of the `temporalDirectory` function and variable are based on the similar `trashItem`, but without the `@discardableResult` annotation (I cannot think of any case where this URL could to be ignored). This closes XcodesOrg#178.
Instead of expanding XIPs on its current directory, a temporal directory is used. The main advantage of this approach is that, because the temporal directory is created on the same volume where Xcode will be installed, the installation is vastly improved if the XIP is on a different volume. - https://nshipster.com/temporary-files/ - The implementation of the `temporalDirectory` function and variable are based on the similar `trashItem`, but without the `@discardableResult` annotation (I cannot think of any case where this URL could to be ignored). This closes XcodesOrg#178.
Sorry to bother you @MattKiazyk, but the PR #179 that closes this has been ready for months. It says that some changes are required, but I made those changes a long time ago. Maybe you've missed this PR because it still says that there're changes requested? |
After PR #126,
xcode install
supports a custom path for Xcode's installation, but this path isn't directly used for the .xip expansion, using instead the same directory where it’s downloaded (~/Library/Application Support/com.robotsandpencils.xcodes/
)1. If this custom installation path is to a different volume than the .xip, this means that:So I think it makes sense to expand the .xip directly on the final volume where Xcode will be installed (probably on the
/.TemporaryItems
folder).Would you accept a pull request for this? Thank you!
Footnotes
I assume this is done to avoid having a partial Xcode installation on the destination folder, which sounds reasonable to me. ↩
The text was updated successfully, but these errors were encountered: