Sustainability of using Github as podspec source

[lukeredpath]

I was wondering what the long-term plan was in terms of where pod specs will be hosted.

The current model, similar to HomeBrew, requires developers to open a pull-request for their spec and then once they have push access, maintain a local clone of the podspec source and keep their specs up-to-date.

I was wondering if this was intended to always be the way that it works or if there was any plan to move towards a more centralised RubyGems style spec server. In this case, instead of having Gemspecs that are used to create gems which are published, we are publishing the specs themselves.

Or is there an intermediate package (like a gem) that could be created from a podspec which is then published; the CocoaPods equivalent of a gem file - a pod file, I guess?

I don't have any real answers at this point but I thought it was something worth discussing. Obviously, if we move towards a Podspec/Pod type distribution then if we use the RubyGems.org source we might get some stuff for free.

[alloy]

Since I also didn’t have any real answers yet I wanted to keep it as simple as possible. I do like simple. But there are definitely pros and cons for both ways and you raise valid points. I’ll have to get back on this next week.

[mackuba]

I'd say if Homebrew uses Github and it works, then you can probably stay with Github for a while. When it gets as popular as RubyGems then you'll worry ;)

[fabiopelosin]

I'm closing this as the current opinion is to eventually migrate CocoaPods to system like ruby gems.