Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run git submodule update after initial clone #406

Closed
wants to merge 6 commits into from
Closed

Run git submodule update after initial clone #406

wants to merge 6 commits into from

Conversation

btaylor
Copy link
Contributor

@btaylor btaylor commented Jul 16, 2012

Some repositories require that submodules be initialized and updated to
be properly built. This is now done during the download phase for every
repository.

This was required for the latest version of the Calabash podspec, which now includes calabash-js as a submodule.

I'm putting this pull request out there looking for feedback. Not sure if we want to add another parameter to specify whether you want submodule support or not, but I figured this was the simplest thing I could put out there and get comments on.

@travisbot
Copy link

This pull request passes (merged 4a5382f into 0920c42).

@alloy
Copy link
Member

alloy commented Jul 17, 2012

I think this is a good idea, but I would like to see a test for this change as well.

@btaylor
Copy link
Contributor Author

btaylor commented Jul 17, 2012

Good idea. Here you go!

Some repositories require that submodules be initialized and updated to
be properly built.  This is now done during the download phase for every
repository.
@fabiopelosin
Copy link
Member

@btaylor Can you update your pull so it can be merged automatically?

@alloy
Copy link
Member

alloy commented Jul 23, 2012

@irrationalfab Oh, actually I already merged this, but forgot to close the ticket. (It didn’t autoclose because I had to rebase myself.)

@alloy alloy closed this Jul 23, 2012
@dulacp
Copy link

dulacp commented Mar 7, 2013

This issue seems to be back, when I run pod spec lint --verbose MySpec.podspec (spec file in this PR) I've got

...
Downloading dependencies

-> Installing MyRepo (0.0.1)
  $ /usr/local/bin/git config core.bare
  true
 > Cloning git repo
   $ /usr/local/bin/git branch --all | grep cocoapods-spec$
     cocoapods-spec
 > Cloning to Pods folder
    $ /usr/local/bin/git clone "/Users/peteralaoui/Library/Caches/CocoaPods/Git/216023ffa3ea0bba86dace88a4b33abee8cbef58" "/tmp/CocoaPods/Lint/Pods/MyRepo"
    Cloning into '/tmp/CocoaPods/Lint/Pods/MyRepo'...
    done.
   $ /usr/local/bin/git remote add upstream 'https://github.com/dulaccc/MyRepo.git'
   $ /usr/local/bin/git fetch -q upstream
   $ /usr/local/bin/git checkout --track -b activated-pod-commit upstream/cocoapods-spec
   Switched to a new branch 'activated-pod-commit'
   Branch activated-pod-commit set up to track remote branch cocoapods-spec from upstream.
   Just downloaded and checked out branch: cocoapods-spec from upstream /Users/peteralaoui/Library/Caches/CocoaPods/Git/216023ffa3ea0bba86dace88a4b33abee8cbef58
 > Using existing documentation
...

There is no sign of git submodule update --init :/
And when I search for the string "update --init" in the cocoapods ruby lib I can't find anything (except in the main Rakefile of the repo)

EDIT I finally found where update --init is called, and it's because of the modularization of cocoapods. But I still got the error, even if I add :submodules => true to the pod dependency line.

@chien
Copy link

chien commented Sep 8, 2013

:submodules => true

works fine for me with CocoaPods 0.23.0

Should we close this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants