-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Matteo Gavagnin
committed
Aug 23, 2013
1 parent
582f10a
commit cfaf9a3
Showing
2 changed files
with
192 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,131 @@ | ||
# | ||
# Be sure to run `pod spec lint MFLocaleManager.podspec' to ensure this is a | ||
# valid spec and to remove all comments including this before submitting the spec. | ||
# | ||
# To learn more about Podspec attributes see http://docs.cocoapods.org/specification.html | ||
# To see working Podspecs in the CocoaPods repo see https://github.com/CocoaPods/Specs/ | ||
# | ||
|
||
Pod::Spec.new do |s| | ||
|
||
# ――― Spec Metadata ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――― # | ||
# | ||
# These will help people to find your library, and whilst it | ||
# can feel like a chore to fill in it's definitely to your advantage. The | ||
# summary should be tweet-length, and the description more in depth. | ||
# | ||
|
||
s.name = "MFLocaleManager" | ||
s.version = "1.0.0" | ||
s.summary = "Classes to change localization on the fly and propagate the setting to every registered label." | ||
|
||
s.description = <<-DESC | ||
MFLocaleManager is a reusable localization manager class for iOS. | ||
It is useful to change in-app localization without having to change iOS language. | ||
It has been originally written by Toni Sala and published by Alberto De Bortoli on GitHub by as [ADBLanguageManager](https://github.com/albertodebortoli/ADBLanguageManager). | ||
Matteo Gavagnin has added the `MFLocalizedLabel`, subclass of `UILabel` that can adapt its content automatically (with a notification) when the language changes. | ||
DESC | ||
|
||
# s.homepage = "http://EXAMPLE/MFLocaleManager" | ||
# s.screenshots = "www.example.com/screenshots_1", "www.example.com/screenshots_2" | ||
|
||
|
||
# ――― Spec License ――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― # | ||
# | ||
# Licensing your code is important. See http://choosealicense.com for more info. | ||
# CocoaPods will detect a license file if there is a named LICENSE* | ||
# Popular ones are 'MIT', 'BSD' and 'Apache License, Version 2.0'. | ||
# | ||
|
||
s.license = 'MIT' | ||
# s.license = { :type => 'MIT', :file => 'FILE_LICENSE' } | ||
|
||
|
||
# ――― Author Metadata ――――――――――――――――――――――――――――――――――――――――――――――――――――――――― # | ||
# | ||
# Specify the authors of the library, with email addresses. Email addresses | ||
# of the authors by using the SCM log. E.g. $ git log. If no email can be | ||
# found CocoaPods accept just the names. | ||
# | ||
|
||
# s.author = { "Matteo Gavagnin" => "[email protected]" } | ||
s.authors = { "Tony Sala" => "[email protected]", "Alberto de Bortoli" => "[email protected]", "Matteo Gavagnin" => "[email protected]" } | ||
# s.author = 'Matteo Gavagnin', 'other author' | ||
|
||
|
||
# ――― Platform Specifics ――――――――――――――――――――――――――――――――――――――――――――――――――――――― # | ||
# | ||
# If this Pod runs only on iOS or OS X, then specify the platform and | ||
# the deployment target. You can optionally include the target after the platform. | ||
# | ||
|
||
# s.platform = :ios | ||
# s.platform = :ios, '5.0' | ||
|
||
# When using multiple platforms | ||
# s.ios.deployment_target = '5.0' | ||
# s.osx.deployment_target = '10.7' | ||
|
||
|
||
# ――― Source Location ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――― # | ||
# | ||
# Specify the location from where the source should be retrieved. | ||
# Supports git, hg, svn and HTTP. | ||
# | ||
|
||
s.source = { :git => "http://github/mobfarm/MFLocaleManager.git", :tag => "1.0.0" } | ||
|
||
|
||
# ――― Source Code ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― # | ||
# | ||
# CocoaPods is smart about how it include source code, for source files | ||
# giving a folder will include any h, m, mm, c & cpp files. For header | ||
# files it will include any header in the folder. | ||
# Not including the public_header_files will make all headers public. | ||
# | ||
|
||
s.source_files = 'Classes', 'Classes/**/*.{h,m}' | ||
s.exclude_files = 'Classes/Exclude' | ||
|
||
# s.public_header_files = 'Classes/**/*.h' | ||
|
||
|
||
# ――― Resources ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― # | ||
# | ||
# A list of resources included with the Pod. These are copied into the | ||
# target bundle with a build phase script. Anything else will be cleaned. | ||
# You can preserve files from being cleaned, please don't preserve | ||
# non-essential files like tests, examples and documentation. | ||
# | ||
|
||
# s.resource = "icon.png" | ||
# s.resources = "Resources/*.png" | ||
|
||
# s.preserve_paths = "FilesToSave", "MoreFilesToSave" | ||
|
||
|
||
# ――― Project Linking ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――― # | ||
# | ||
# Link your library with frameworks, or libraries. Libraries do not include | ||
# the lib prefix of their name. | ||
# | ||
|
||
# s.framework = 'SomeFramework' | ||
# s.frameworks = 'SomeFramework', 'AnotherFramework' | ||
|
||
# s.library = 'iconv' | ||
# s.libraries = 'iconv', 'xml2' | ||
|
||
|
||
# ――― Project Settings ――――――――――――――――――――――――――――――――――――――――――――――――――――――――― # | ||
# | ||
# If your library depends on compiler flags you can set them in the xcconfig hash | ||
# where they will only apply to your library. If you depend on other Podspecs | ||
# you can include multiple dependencies to ensure it works. | ||
|
||
# s.requires_arc = true | ||
|
||
# s.xcconfig = { 'HEADER_SEARCH_PATHS' => '$(SDKROOT)/usr/include/libxml2' } | ||
# s.dependency 'JSONKit', '~> 1.4' | ||
|
||
end |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,62 @@ | ||
SpecsPrivate | ||
============ | ||
# A repository of CocoaPods specifications. | ||
|
||
[](http://travis-ci.org/CocoaPods/Specs) | ||
|
||
This repository contains specifications of open-source Objective-C libraries, which are used by [CocoaPods](https://github.com/CocoaPods/CocoaPods) to manage library dependencies for your Xcode project. | ||
|
||
|
||
## Creating specifications | ||
|
||
First of all, you need to install the tools. | ||
|
||
```console | ||
$ [sudo] gem install cocoapods | ||
``` | ||
|
||
Then you can have the CocoaPods `pod` command create a stub specification: | ||
|
||
```console | ||
$ 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](http://www.ruby-lang.org/) source file. | ||
|
||
```console | ||
$ 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. | ||
|
||
```console | ||
$ pod spec lint Bananas.podspec --verbose | ||
``` | ||
|
||
Once you have created a working specification create a pull request. | ||
|
||
### 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](http://semver.org/). See this [example](https://github.com/CocoaPods/Specs/wiki/Cross-dependencies-resolution-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](https://github.com/CocoaPods/Specs/wiki/%22Please-add-semantic-version-tags%22-issue-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](http://travis-ci.org/#!/CocoaPods/Specs))_ | ||
|
||
## License | ||
|
||
These specifications and CocoaPods are available under the [MIT license](http://www.opensource.org/licenses/mit-license.php). | ||
|
||
|
||
Our private Specs repository |