Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Explicitly specify spec repos to load from and the order #85

Closed
alloy opened this Issue Nov 22, 2011 · 3 comments

Comments

Projects
None yet
4 participants
Owner

alloy commented Nov 22, 2011

From @mmobarak:

Another idea for allowing overrides of podspecs is to allow the inclusion of an ordered repo list at the start of the Podfile, in the style of the Gemfile 'source' directive. This would then determine the order in which the pod repos were searched, and maybe eventually download remote repos to cache the podspecs locally:

repo  'mycompanypodspecs'                      # the mycompanypodspecs repo in ~/.cocoapods, 
                                               # installed/managed with 'pod repo', is preferred

repo  'https://github.com/CocoaPods/Specs.git' # the generally authoritative podspec repo 
                                               # downloaded as necessary to ~/.cocoapods 
                                               # subject to management with 'pod repo'
Contributor

atomkirk commented Aug 18, 2012

just search all repos and use the one with the highest version

A workaround: The search for the repo to use seems to be alphabetical. You can implicitly specify the order by choosing the repo name in pod repo add.

I would also prefer that it just searches all repos and uses the highest version.

Owner

alloy commented Sep 3, 2012

@atomkirk Agreed.

@ghost ghost assigned fabiopelosin Sep 21, 2012

jzapater pushed a commit to jzapater/CocoaPods that referenced this issue Sep 17, 2013

Merge pull request #85 from Tylerc230/master
MagicalRecord git url must use https not http

fabiopelosin added a commit that referenced this issue Oct 25, 2014

fabiopelosin added a commit that referenced this issue Oct 25, 2014

Merge pull request #85 from dlackty/social-media-lint
Check social_media_url changed from default value
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment