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

Skip clone gem when passed 'GEMSRC_SKIP' #15

Merged
merged 1 commit into from
Aug 1, 2016

Conversation

unasuke
Copy link
Contributor

@unasuke unasuke commented Jul 31, 2016

I use bundle install --force command often for re-install several gems.
It takes much time by non cloneable url in gemspec.
Or, sometimes want to skip clone explicitly.

in my case

bundle install --force

% time bundle install --force
Installing rake 11.2.2
    exists /Users/unasuke/src/github.com/ruby/rake
(snip)...
Bundle complete! 28 Gemfile dependencies, 97 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.
bundle install --force  48.37s user 26.60s system 24% cpu 5:11.44 total

mean of 5 times : 5:07.43

GEMSRC_SKIP=true bundle install --force

% time GEMSRC_SKIP=true bundle install --force
Installing rake 11.2.2
Installing concurrent-ruby 1.0.2
(snip)...
Bundle complete! 28 Gemfile dependencies, 97 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.
GEMSRC_SKIP=true bundle install --force  42.75s user 20.86s system 99% cpu 1:03.72 total

mean of 5 times : 1:04.55

If you know that already exist cloned repository or
you want to ignore gem-src by some reason,
you can skip cloning step by gem-src.

e.g. `GEMSRC_SKIP=true bundle install`
@amatsuda
Copy link
Owner

amatsuda commented Aug 1, 2016

@unasuke Thank you, I like this!

@amatsuda amatsuda merged commit b1da812 into amatsuda:master Aug 1, 2016
@unasuke unasuke deleted the skip_clone_repository branch August 1, 2016 01:53
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.

2 participants