You can clone with
HTTPS or Subversion.
I came across a weird bug with subspecs / specific commit dependencies.
Basically pod install doesn't use the correct revision of a dependency after removing a directory in Pods.
I'm using CocoaPods 0.14.0.
Here's a test podfile to reproduce the issue:
platform :ios, :deployment_target => '5.0'
pod 'TestProject/SubLib', :git => 'firstname.lastname@example.org:jeanregisser/DummyTestProject.git'
Now if you pod install --verbose --no-clean you'll end up with libPusher checked out at lukeredpath/libPusher@e262c4b
And this is expected since TestProject.podspec declares this specific revision.
pod install --verbose --no-clean
So, now just rm -rf Pods/libPusher and again pod install --verbose --no-clean.
You'll end up with libPusher checked out at lukeredpath/libPusher@d4d51f8 (which is the tagged version 1.3 specified in https://github.com/CocoaPods/Specs/blob/master/libPusher/1.3/libPusher.podspec) and this is wrong.
rm -rf Pods/libPusher
Let me know if you need more info from my setup.
This bug still exists with CocoaPods 0.15.1
Closed by 0.17 branch.
[Sandbox] Clean up.
This includes a fix for an issue which caused the use of the incorrect
specification for dependencies from external sources.