Skip to content

ipup/Specs

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

A repository of CocoaPods specifications.

Build Status

This repository contains specifications of open-source Objective-C libraries, which are used by CocoaPods to manage library dependencies for your Xcode project.

Creating specifications

First of all, you need to install the tools.

$ [sudo] gem install cocoapods

Then you can have the CocoaPods pod command create a stub specification:

$ pod spec create Bananas
$ pod spec create https://github.com/Bananas/Bananas # For libraries hosted on GitHub

Now edit the stub specification following the explanations therein contained. This file is a Ruby source file.

$ vim Bananas.podspec

You can verify the specification file with the lint command. This command checks for common errors and whether the pod builds on the platforms that it supports.

$ pod spec lint Bananas.podspec --verbose

Once you have created a working specification create a pull request. Once accepted, you will receive push access to this repo. Feel free to push updates, specs for other libraries you use, and participate in other tickets.

If you have push access you can publish all the podspecs in a working directory.

$ pod setup --push # Run only once
$ pod push master

Namespacing

A specification file has to be namespaced by the library’s name and the version for which the specification is meant. For instance, the directory for a library named ‘Bananas’ with version ‘1.2.3’ should be:

$ mkdir -p Bananas/1.2.3
$ cd Bananas/1.2.3

Versioning

CocoaPods uses a versioning scheme known as Semantic Versioning. See this example for more info on why this scheme is used.

If the library, that you are creating a specification for, does not yet have any tagged versions in its repo, then it’s best to start with the lowest version ‘0.0.1’, which will ensure that once the author does add tagged versions they will be equal or higher than ‘0.0.1’. It is your responsibility to ask the author of the library to tag versions, luckily we have a template for this.

Check the entire repo

You can also verify the entire set by running the rake task.

$ rake lint

(Note: this is run on every commit by Travis)

License

These specifications and CocoaPods are available under the MIT license.