-
Notifications
You must be signed in to change notification settings - Fork 53
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
Dealing with Alcatraz and CocoaPods #26
Comments
There is a conversation about how to deal with the situation at alcatraz/alcatraz-packages#69. |
Great thanks! I didn't see that one. As is, it mean we cannot install KFCocoaPodsPlugin through Alcatraz right? |
Yes, sad but true. I hope there will be a solution soon. |
@ricobeck i recommend vendoring stuff manually (at least in a branch) for now, and avoiding CocoaPods until we support binary distribution. I'll put it on the priority list. |
I think this is a two part problem. See also the issue here: alcatraz/Alcatraz#140
Should alcatraz allow cocoa pods dependencies? If so KFCocoaPodsPlugin should not change. If alcatraz though should not depend on CocoaPods, KFCocoaPodsPlugin would need to change to include the Pods in the repo such that running cocoa pods is not required.
In anycase alcatraz/Alcatraz#140 must be resolved first, as KFCocoaPodsPlugin depends on being built as a workspace.
The text was updated successfully, but these errors were encountered: