问题
I used CocoaPods for some of my projects. It's cool and easy to keep updated with my dependencies/open source frameworks.
But I have some doubts regarding the inner workings of CocoaPods.
In our Podfile we are giving only the the name of pods, sometimes the version also,like
pod "AFNetworking" , "1.3.2"
Then it correctly finds and clones the AFNetworking repo. How this is work? How the ruby gems know the actual repository is in Github. Are pods work with Github only? (Because I saw pods for only frameworks available on Github). If we can use pods for dependencies in other than Github (eg from Bitbuket), how can we add that pod to our Podfile?
回答1:
CocoaPods does a whole lot behind the scenes to make everything you're talking about work. On a relatively high level the actual 'Pods' are managed in a repo that lives on Github here. This is where 3rd party library vendors submit their 'Pods' to work with CocoaPods. You'll notice that if you search for a Pod using the command line tool with pod search AFNetworking you will see all the available Pods matching your search term.
As far as Github vs other sites goes even though the repository full of CocoaPods specifications lives on Github, CocoaPods itself uses just plain old Git to pull down the source from the given repository. Because of this you could make specs from any git repo hosted on any site. We also support svn, mercurial and just plain old http(s). If you're interested in how the specs work overall you can look at some in the specs repo you can open them from ~/.cocoapods/repos/master on your local machine or edit one directly with pod spec edit AFNetworking from the command line.
回答2:
CocoaPods is a centralised dependency management. It operates by Podfile to read a dependency and a version. Pod project will be created in a workspace. CocoaPods implements Implicitly dependency[About] approach:
Source codeClosed code[Example]
On the client side you have a Podfile. The core of Podfile is a pod:
- name
- version - Semantic versioning
When Podfile is read (during pod install or pod update) by Cocoapods the graph of implicit and explicit dependencies is created. After that the manager should find each source into a .podspec which is usually hosted into some host. That is why Cocoapods is centralised. A framework's developer is responsible for creating this file and supporting it. .podspec describes a meta-information about the framework, like dependencies, subspecs, etc. The main part of it is source which tells to Cocoapods where source is hosted and this sources will be downloaded into a Pod project. Cocoapods uses workspace to automate the build process and manage implicit dependencies. Cocoapods setup all necessary info into your consumer project(like Search pats, etc). When you build the consumer project Xcode pull pods and assemble all together.
Local podspec
CocoaPods vs Carthage
CocoaPods version
来源：https://stackoverflow.com/questions/18917137/how-does-cocoapods-work