Permalink
Browse files

Misc updates

  • Loading branch information...
1 parent b1c84b7 commit 68f2926f54f7d79d1d445f29cddcf3d6f316d757 @fabiopelosin fabiopelosin committed Feb 26, 2013
View
@@ -1,4 +1,4 @@
-source :rubygems
+source 'https://rubygems.org'
gem 'middleman', "~>3.0.5"
gem 'redcarpet'
View
@@ -1,10 +1,10 @@
GEM
- remote: http://rubygems.org/
+ remote: https://rubygems.org/
specs:
- activesupport (3.2.9)
+ activesupport (3.2.12)
i18n (~> 0.6)
multi_json (~> 1.0)
- chunky_png (1.2.6)
+ chunky_png (1.2.7)
claide (0.2.0)
coffee-script (2.2.0)
coffee-script-source
@@ -16,49 +16,48 @@ GEM
sass (~> 3.1)
execjs (1.4.0)
multi_json (~> 1.0)
- ffi (1.2.0)
- fssm (0.2.9)
- github-markup (0.7.4)
- haml (3.1.7)
+ fssm (0.2.10)
+ github-markup (0.7.5)
+ haml (4.0.0)
+ tilt
hike (1.2.1)
http_router (0.10.2)
rack (>= 1.0.0)
url_mount (~> 0.2.1)
- i18n (0.6.1)
- listen (0.5.3)
+ i18n (0.6.2)
+ listen (0.7.3)
maruku (0.6.1)
syntax (>= 1.0.0)
- middleman (3.0.6)
- middleman-core (= 3.0.6)
- middleman-more (= 3.0.6)
- middleman-sprockets (~> 3.0.2)
- middleman-core (3.0.6)
+ middleman (3.0.12)
+ middleman-core (= 3.0.12)
+ middleman-more (= 3.0.12)
+ middleman-sprockets (~> 3.0.8)
+ middleman-core (3.0.12)
activesupport (~> 3.2.6)
bundler (~> 1.1)
- listen (~> 0.5.2)
+ listen (~> 0.7.3)
rack (~> 1.4.1)
rack-test (~> 0.6.1)
- rb-fsevent (~> 0.9.1)
- rb-inotify (~> 0.8.8)
+ rb-fsevent (~> 0.9.3)
thor (~> 0.15.4)
tilt (~> 1.3.1)
- middleman-more (3.0.6)
+ middleman-more (3.0.12)
coffee-script (~> 2.2.0)
coffee-script-source (~> 1.3.3)
compass (>= 0.12.2)
execjs (~> 1.4.0)
haml (>= 3.1.6)
i18n (~> 0.6.0)
maruku (~> 0.6.0)
- middleman-core (= 3.0.6)
+ middleman-core (= 3.0.12)
padrino-helpers (= 0.10.7)
sass (>= 3.1.20)
uglifier (~> 1.2.6)
- middleman-sprockets (3.0.4)
- middleman-more (~> 3.0.1)
+ middleman-sprockets (3.0.8)
+ middleman-more (>= 3.0.11)
sprockets (~> 2.1, < 2.5)
- sprockets-sass (~> 0.8.0)
- multi_json (1.3.7)
+ sprockets-sass (~> 0.9.1)
+ multi_json (1.6.1)
padrino-core (0.10.7)
activesupport (~> 3.2.0)
http_router (~> 0.10.2)
@@ -69,32 +68,30 @@ GEM
i18n (~> 0.6)
padrino-core (= 0.10.7)
posix-spawn (0.3.6)
- pygments.rb (0.3.2)
+ pygments.rb (0.4.2)
posix-spawn (~> 0.3.6)
yajl-ruby (~> 1.1.0)
- rack (1.4.1)
- rack-protection (1.2.0)
+ rack (1.4.5)
+ rack-protection (1.3.2)
rack
rack-test (0.6.2)
rack (>= 1.0)
- rb-fsevent (0.9.2)
- rb-inotify (0.8.8)
- ffi (>= 0.5.0)
+ rb-fsevent (0.9.3)
redcarpet (2.2.2)
- sass (3.2.3)
- sinatra (1.3.3)
- rack (~> 1.3, >= 1.3.6)
- rack-protection (~> 1.2)
+ sass (3.2.6)
+ sinatra (1.3.5)
+ rack (~> 1.4)
+ rack-protection (~> 1.3)
tilt (~> 1.3, >= 1.3.3)
- slim (1.3.4)
+ slim (1.3.6)
temple (~> 0.5.5)
tilt (~> 1.3.3)
sprockets (2.4.5)
hike (~> 1.2)
multi_json (~> 1.0)
rack (~> 1.0)
tilt (~> 1.1, != 1.3.0)
- sprockets-sass (0.8.0)
+ sprockets-sass (0.9.1)
sprockets (~> 2.0)
tilt (~> 1.1)
syntax (1.0.0)
@@ -107,7 +104,7 @@ GEM
url_mount (0.2.1)
rack
yajl-ruby (1.1.0)
- yard (0.8.3)
+ yard (0.8.5)
PLATFORMS
ruby
View
@@ -3,6 +3,18 @@ cocoapods.github.com
User and developer documentation for CocoaPods.
+## Information Sources
+
+This application gathers information from the following sources:
+
+- Guides: https://github.com/CocoaPods/cocoapods.github.com/tree/develop/guides
+- Podfile: https://github.com/CocoaPods/Core/blob/master/lib/cocoapods-core/podfile/dsl.rb
+- Specification: https://github.com/CocoaPods/Core/blob/master/lib/cocoapods-core/specification/dsl.rb
+- Command Line: https://github.com/CocoaPods/CocoaPods/tree/master/lib/cocoapods/command
+
+If you find any area which could be improved, pull requests are welcome and
+make good karma.
+
## Architecture
This application builds a static site by using the [Middleman](http://middlemanapp.com).
View
@@ -123,18 +123,28 @@ namespace :generate do
end
task :all => [:dsl, :gems, :commands, :search]
+ task :default => 'all'
end
#-----------------------------------------------------------------------------#
-desc "Generates the data for the commands."
-task :build => 'generate:all' do
- sh "middleman build"
+namespace :middleman do
+
+ desc "Builds the site with middleman."
+ task :build => 'generate:all' do
+ sh "middleman build"
+ end
+
+ desc "Builds the site with middleman."
+ task :server do
+ sh "middleman"
+ end
+
end
#-----------------------------------------------------------------------------#
-desc "deploy build directory to github pages"
+desc "creates the build directory which contains the master branch"
task :bootstrap_build do
FileUtils.rm_rf 'build'
sh 'git clone git@github.com:CocoaPods/cocoapods.github.com.git build'
@@ -146,6 +156,7 @@ desc "deploy build directory to github pages"
task :deploy do
puts "\e[1;33mDeploying branch to master brach\e[0m"
cd "build" do
+ sh "git pull"
sh "git add ."
sh "git add -u"
sh "git commit -m 'Site updated at #{Time.now.utc}'"
View
@@ -21,11 +21,10 @@
set :markdown, {
:fenced_code_blocks => true,
:autolink => true,
- :smartypants => true }
+ :smartypants => true
+}
activate :automatic_image_sizes
-#--------------------------------------#
-
#------------------------------------------------------------------------------#
Submodule CocoaPods updated 540 files
View
1 guides
@@ -70,6 +70,12 @@ def command_groups
"pod repo lint",
"pod setup",
],
+
+ 'IPC' => [
+ "pod ipc spec",
+ "pod ipc podfile",
+ "pod ipc list",
+ ],
}
end
View
@@ -1,3 +1,5 @@
+require 'active_support'
+
module NavigationHelpers
# The title of the current page. If not specified with YAML
@@ -10,14 +12,11 @@ module NavigationHelpers
def page_title(resource = nil)
resource ||= current_resource
- resource.metadata[:page]['title'] \
- ||
- resource.metadata[:locals][:code_object] && resource.metadata[:locals][:code_object].name \
- ||
- resource.metadata[:locals][:name] \
- ||
- (warn "[WARN] Missing title for resource #{resource.path}"
- File.basename(resource.path, ".html"))
+ title = resource.metadata[:page]['title']
+ title ||= resource.metadata[:locals][:code_object].name if resource.metadata[:locals][:code_object]
+ title ||= resource.metadata[:locals][:name]
+ title ||= File.basename(resource.path, ".html").to_s.humanize
+ title.to_s.gsub('cocoapods', 'CocoaPods')
end
@@ -150,8 +149,7 @@ def _columnize_algorithmically(groups, only_public, show_empty_groups)
groups_and_methods = []
# methods_by_group = methods.group_by(&:group)
- groups.each do |group|
- puts group.name
+ groups.each do |group|
if !group.meths.nil? || !group.meths.empty? || show_empty_groups
groups_and_methods << group
groups_and_methods.concat(group.meths)
@@ -233,7 +231,7 @@ def linkify_from_obect(object, base_object)
#
def link_doc_string(html)
return nil unless html
- html.gsub(/\{([^\}]+)\}/) do |match|
+ html.force_encoding('utf-8').gsub(/\{([^\}]+)\}/) do |match|
"<code>#{linkify(match[1..-2])}</code>"
end
end
@@ -242,4 +242,13 @@ $footer_height : 100px
font-size : 12px
margin : 0 -92px
+// TODO /////////////////////////////////////////////////////////////////////
+
+
+.link-list
+ h3
+ margin-top: 40px
+
+ a
+ color: #8C7A73
@@ -1,23 +0,0 @@
-## Dependency version workflow
-There is, unfortunately, often an issue of devs not interpreting version numbers well or assigning emotional value to certain version numbers.
-
-However, arbitrary revisions as version is not a good idea for a library manager vs a proper version number (see [Semantic Versioning](http://semver.org)). Let me explain how, in an ideal world ;), I’d prefer people to interact with it:
-
-* “I want to start using CocoaLumberjack, the current version will be fine for now.” So the dev adds a dependency on the lib _without_ a version requirement and lets the manager install it which will use the latest version:
-
- pod 'CocoaLumberjack'
-
-* Some time into the future, the dev wants to update the dependencies so runs the install command again, which will now install the version of the lib which is the latest version _at that time_.
-
-* At some point the dev is finished on the client work (or a newer version of the lib changes the API and the changes aren’t needed) so the dev adds a version requirement to the dependency. For instance, consider that the author of the lib follows the semver guidelines, you can somewhat trust that between ‘1.0.7’ and ‘1.1.0’ **no** API changes will be made, but only bug fixes. So instead of requiring a specific version, the dev can specify that _any_ ‘1.0.x’ is allowed as long as it’s higher than ‘1.0.7’:
-
- pod 'CocoaLumberjack', '~> 1.0.7'
-
-
-The point is that devs can easily keep track of newer versions of dependencies, by simply running `pod install` again, which they might otherwise do less if they had to change everything manually.
-
-### CocoaPods Versioning Specifics
-
-CocoaPods uses RubyGems versions for specifying pod spec versions. The [RubyGems Versioning Policies](http://docs.rubygems.org/read/chapter/7) describes the rules used for interpreting version numbers. The [RubyGems version specifiers](http://docs.rubygems.org/read/chapter/16#page74) describe exactly how to use the comparison operators which specify dependency versions.
-
-Following the pattern established in RubyGems, pre-release versions can also be specified in CocoaPods. A pre-release of version 1.2, for example, can be specified by '1.2.beta.3'. In this example, the dependency specifier '~> 1.2.beta' will match '1.2.beta.3'.
@@ -1,18 +1,18 @@
-# Contributing to the master repo
-
- This guide is a stub
-
+## Contributing to the master repo
The master repo contains specifications of open-source Objective-C libraries.
-## Details
+### Details
- installation path: `~/.cocoapods/master`
- home: https://github.com/CocoaPods/Specs
-## Contributing
+### Contributing
-To ensure a high quality and reliable collection of Pods the master repo is strict about the acceptable specifications. The CocoaPods linter (see the `pod spec lint` command) is used to validate specification and no errors or warnings are accepted.
+To ensure a high quality and reliable collection of Pods the master repo is
+strict about the acceptable specifications. The CocoaPods linter (see the `pod
+spec lint` command) is used to validate specification and no errors or warnings
+are accepted.
The highest priority of the master repo is to guarantee the integrity of existing
CocoaPods installations.
@@ -29,7 +29,7 @@ CocoaPods uses a versioning scheme known as [Semantic
Versioning](http://semver.org/), necessary for [cross resolution of
dependencies](https://github.com/CocoaPods/Specs/wiki/Cross-dependencies-resolution-example).
-## Unversioned libraries
+### Unversioned libraries
One of the CocoaPods goals is to promote the discovery of open-source software,
for this reason new Pods for libraries which are not versioned are accepted in
@@ -55,7 +55,7 @@ If you need to update an unversione library you can:
- Create a podspec and use it in a private repo.
-## Creating podspecs
+### Creating podspecs
Creating a podspec is very easy as we provide templates full of examples.
@@ -71,7 +71,7 @@ A this point you need edit compile the template (a pod specification is a Ruby s
$ pod spec lint Bananas.podspec --verbose
-## Sharing podspecs
+### Sharing podspecs
When a podspec lints you can submit it to the master repo.
@@ -1,4 +1,4 @@
-## Creation
+## Creating and maintaining a pod
The following file structure is suggested:
@@ -1,3 +1,5 @@
+## Creating your own repository
+
A specification repository is a simple collection of podspec files organized with the following structure:
```
Oops, something went wrong.

0 comments on commit 68f2926

Please sign in to comment.