-
-
Notifications
You must be signed in to change notification settings - Fork 57
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
Rome fails with binary references in Cartfile.resolved, still exits cleanly #58
Comments
@erichoracek binary repos are not supported at the moment. I was unaware of this feature in Carthage. I will add support for binary only frameworks, I need to study a little how deal with this case. I'll also correct the exit status on parse errors. |
Is there any reason why Rome would need to cache prebuilt frameworks for |
I guess a few reasons could be:
I can start with trying to tolerate parse errors in the |
Carthage has an internal cache for prebuilt binaries at:
so I don't think that you'd be avoiding unnecessary downloads. As such, as far as I can tell, the only benefit that Rome support for The ideal behavior for us would just be to ignore these frameworks outright since we don't care about having these frameworks stored in our bucket. However, I can see how that may be unexpected behavior for some users. |
I think a download can be avoided if the frameworks is placed directly at the correct path in To make this work properly I think that Rome would need to resolve the binary json and figure out a couple of things. After that it would generate a Immediate plan:
Further enhancement:
|
That seems reasonable—as long as |
Please try pre-release https://github.com/blender/Rome/releases/tag/v0.10.2.23 |
@blender that fixed it, thanks! |
There is a full new release that includes this fix and #57 , get it with |
When the Cartfile.resolved contains a binary framework, e.g.:
Rome emits the following error when attempting to perform a download:
Additionally, when this occurs, Rome does not error with a non-zero exit status to indicate that an error occurred. This causes scripts to continue as if no error occurred.
This was tested with the latest Rome version:
The text was updated successfully, but these errors were encountered: