add podspec file in git repo

[prabirshrestha]

This would easily allow us to consume ReactiveCocoa by adding the following code in our Podfile.

platform :ios
pod "ReactiveCocoa", :git => 'https://github.com/github/ReactiveCocoa.git', :tag => 'v0.8.0'

[sarahhodne]

This would really help using ReactiveCocoa with CocoaPods. I would like using master, but there's not really a way to do that now without cloning ReactiveCocoa. I'm using Mantle as well in my project, which is in my CocoaPods repo, but they don't play nicely together as they have some shared dependencies, which leads to duplicated symbols in the linked binary.

[jspahrsummers]

Isn't CocoaPods supposed to handle that case? I thought that was a pretty big selling point. In any case, linking without -all_load should solve duplicate symbol errors.

We've been pretty diligent about tagging, and others (like @irrationalfab) have been maintaining a Podspec external to the repo.

[jspahrsummers]

So, just to clarify: are tags usable without the podspec file being in the repo?

[prabirshrestha]

@irrationalfab thoughts on this?

[dannygreg]

As far as I understand in our current state we are 100% usable with CocoaPods right now. I see no need to add another file to the repo.

[fabiopelosin]

This would really help using ReactiveCocoa with CocoaPods. I would like using master, but there's not really a way to do that now without cloning ReactiveCocoa.

I agree with @jspahrsummers that they have been doing a great job with tagging so I personally see little need of using the head of master. In any case, if you need it, you can create a custom podspec in a private repo (however you might need to update the file patterns from time to time).

Isn't CocoaPods supposed to handle that case? I thought that was a pretty big selling point.

If a library is added to a project manually CocoaPods it is not aware of it and doesn't have the information necessary to cross resolve dependencies.

So, just to clarify: are tags usable without the podspec file being in the repo?

Yes. When a library is properly tagged the only advantage of having a podspec in the repo is that users can edit the library from their final application (:local option) to facilitate the preparation of a pull request. However if the podspec is added to the root of the repo it is expected to be maintained, otherwise it is useless.

[jspahrsummers]

@irrationalfab Thanks for the summary and your work on the podspec!

I agree with @dannygreg, so I'm going to close this out.