Permalink
Browse files

Renamed links to alloy/cocoapods to CocoaPods/CocoaPods and also allo…

…y/cocoapods-specs to CocoaPods/Specs.
  • Loading branch information...
1 parent 2ab89bd commit 7945c246a2d2793c71d866a4055fd3e01ee5bbeb @floere floere committed Nov 12, 2011
Showing with 15 additions and 15 deletions.
  1. +9 −9 README.md
  2. +1 −1 cocoapods.gemspec
  3. +1 −1 lib/cocoapods/command.rb
  4. +2 −2 lib/cocoapods/command/setup.rb
  5. +1 −1 lib/cocoapods/podfile.rb
  6. +1 −1 spec/unit/command_spec.rb
View
@@ -6,7 +6,7 @@ You specify the dependencies for your project in one easy text file. CocoaPods r
Ultimately, the goal is to improve discoverability of, and engagement in, third party open-source libraries, by creating a more centralized ecosystem.
-See [the wiki](https://github.com/alloy/cocoapods/wiki) for more in depth information on several topics.
+See [the wiki](https://github.com/CocoaPods/CocoaPods/wiki) for more in depth information on several topics.
## Installation
@@ -34,19 +34,19 @@ Search for Pods by name or description.
$ pod search asi
==> ASIHTTPRequest (1.8.1)
Easy to use CFNetwork wrapper for HTTP requests, Objective-C, Mac OS X and iPhone
-
+
==> ASIWebPageRequest (1.8.1)
The ASIWebPageRequest class included with ASIHTTPRequest lets you download
complete webpages, including external resources like images and stylesheets.
-After you've found your favorite dependencies you add them to your [Podfile](https://github.com/alloy/cocoapods/wiki/A-Podfile).
+After you've found your favorite dependencies you add them to your [Podfile](https://github.com/CocoaPods/CocoaPods/wiki/A-Podfile).
$ edit Podfile
platform :ios
dependency 'JSONKit', '~> 1.4'
dependency 'Reachability', '~> 2.0.4'
-And then you [install the dependencies](https://github.com/alloy/cocoapods/wiki/Creating-a-project-that-uses-CocoaPods) in your project.
+And then you [install the dependencies](https://github.com/CocoaPods/CocoaPods/wiki/Creating-a-project-that-uses-CocoaPods) in your project.
$ pod install App.xcodeproj
@@ -56,20 +56,20 @@ Remember to always open the Xcode workspace instead of the project file when you
$ open App.xcworkspace
-Sometimes CocoaPods doesn't have a Pod for one of your dependencies yet. Fortunately [creating a Pod](https://github.com/alloy/cocoapods/wiki/A-pod-specification) is really easy.
+Sometimes CocoaPods doesn't have a Pod for one of your dependencies yet. Fortunately [creating a Pod](https://github.com/CocoaPods/CocoaPods/wiki/A-pod-specification) is really easy.
$ pod spec create Peanuts
$ edit Peanuts.podspec
$ pod spec lint Peanuts.podspec
-Once you've got it running [create a ticket](https://github.com/alloy/cocoapods/issues) and upload the Pod. If you're familiar with Git you can also fork the [CocoaPods specs](https://github.com/alloy/cocoapods-specs) repository and send a pull request. We really love contributions!
+Once you've got it running [create a ticket](https://github.com/CocoaPods/CocoaPods/issues) and upload the Pod. If you're familiar with Git you can also fork the [CocoaPods specs](https://github.com/CocoaPods/Specs) repository and send a pull request. We really love contributions!
-There are several other ways to start using **any** library without a Pod specification, which can be seen in the [SSCatalog example](https://github.com/alloy/cocoapods/blob/master/examples/SSCatalog/Podfile).
+There are several other ways to start using **any** library without a Pod specification, which can be seen in the [SSCatalog example](https://github.com/CocoaPods/CocoaPods/blob/master/examples/SSCatalog/Podfile).
## Collaborate
-All CocoaPods development happens on GitHub, there is a repository for [CocoaPods](https://github.com/alloy/cocoapods) and one for the [CocoaPods specs](https://github.com/alloy/cocoapods-specs). Contributing patches or Pods is really easy and gratifying. You even get push access when one of your specs or patches is accepted.
+All CocoaPods development happens on GitHub, there is a repository for [CocoaPods](https://github.com/CocoaPods/CocoaPods) and one for the [CocoaPods specs](https://github.com/CocoaPods/Specs). Contributing patches or Pods is really easy and gratifying. You even get push access when one of your specs or patches is accepted.
Follow [@CocoaPodsOrg](http://twitter.com/CocoaPodsOrg) to get up to date information about what's going on in the CocoaPods world.
@@ -84,6 +84,6 @@ If you're really oldschool and you want to discuss CocoaPods development you can
* “Anybody who has tasted the coolness of RubyGems (and @gembundler) understands how cool CocoaPods might be.” –– [StuFF mc](http://twitter.com/#!/stuffmc/status/115374231591731200)
* “I will be working on getting several of my Objective-C libraries ready for CocoaPods this week!” –– [Luke Redpath](http://twitter.com/#!/lukeredpath/status/115510581921988608)
* “Really digg how @alloy is building a potential game changer” –– [Klaas Speller](https://twitter.com/#!/spllr/status/115914209438601216)
-* “@alloy's making an Objective-C package manager: github.com/alloy/cocoapods. This is fantastic news kids!” –– [Josh Abernathy](http://twitter.com/#!/joshaber/status/115273577703555073)
+* “@alloy's making an Objective-C package manager: github.com/CocoaPods/CocoaPods. This is fantastic news kids!” –– [Josh Abernathy](http://twitter.com/#!/joshaber/status/115273577703555073)
* “A package manager for Cocoa/Objective-C, built with @MacRuby. Awesomeness!” –– [Johannes Fahrenkrug](http://twitter.com/#!/jfahrenkrug/status/115303240286998528)
* “This is awesome, I love endorsements!” –– [Appie Durán](http://twitter.com/#!/AppieDuran)
View
@@ -7,7 +7,7 @@ Gem::Specification.new do |s|
s.date = "2011-09-17"
s.license = "MIT"
s.email = "eloy.de.enige@gmail.com"
- s.homepage = "https://github.com/alloy/cocoapods"
+ s.homepage = "https://github.com/CocoaPods/CocoaPods"
s.authors = ["Eloy Duran"]
s.summary = "A simple Objective-C library package manager. (Requires MacRuby.)"
View
@@ -52,7 +52,7 @@ def self.run(*argv)
rescue Exception => e
unless e.is_a?(Informative)
puts "Oh no, an error occurred. Please run with `--verbose' and report " \
- "on https://github.com/alloy/cocoapods/issues."
+ "on https://github.com/CocoaPods/CocoaPods/issues."
puts ""
end
puts e.message
@@ -9,15 +9,15 @@ def self.banner
Creates a directory at `~/.cocoapods' which will hold your spec-repos.
This is where it will create a clone of the public `master' spec-repo from:
- https://github.com/alloy/cocoapods-specs}
+ https://github.com/CocoaPods/Specs}
end
def initialize(argv)
super unless argv.empty?
end
def master_repo_url
- 'git://github.com/alloy/cocoapods-specs.git'
+ 'git://github.com/CocoaPods/Specs.git'
end
def add_master_repo_command
View
@@ -134,7 +134,7 @@ def platform(platform = nil)
#
#
# For more info on the definition of a Pod::Specification see:
- # https://github.com/alloy/cocoapods/wiki/A-pod-specification
+ # https://github.com/CocoaPods/CocoaPods/wiki/A-pod-specification
#
#
def dependency(*name_and_version_requirements, &block)
@@ -15,7 +15,7 @@
it "returns the URL of the `master' spec-repo" do
command = Pod::Command::Setup.new(argv)
- command.master_repo_url.should == 'git://github.com/alloy/cocoapods-specs.git'
+ command.master_repo_url.should == 'git://github.com/CocoaPods/Specs.git'
end
end

0 comments on commit 7945c24

Please sign in to comment.