CocoaPods/CocoaPods — Issue #94: CocoaPods workflow should be invisible to end-users
Author: schwa
Created: 2011-12-07 21:59:52+00:00
State: open

After testing CocoaPods it seems it builds an "umbrella" xcworkspace that is responsible for building the dependencies and the original Xcode project.

In my opinion this is not an ideal situation. It seems to me if you want Cocoa Pods to be accepted by the developer community you should be striving to work with the developer's existing workflow. Requiring a developer to dramatically change the way he/she works just to use CocoaPods isn't an acceptable solution in my opinion.

Reasons why this change could be a problem include (but are not limited to) breakage of pre-existing scripts and/or breaking of pre-existing workspace configurations.

To be honest the CocoaPods solution seems very ungraceful and a bit of a hack. Have other alternatives been explored?