Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

Check for gems missing in sources before pulling the gem source #111

Closed
KieranP opened this issue Feb 20, 2010 · 2 comments
Closed

Check for gems missing in sources before pulling the gem source #111

KieranP opened this issue Feb 20, 2010 · 2 comments

Comments

@KieranP
Copy link

KieranP commented Feb 20, 2010

Don't fetch source index unless needed. The index takes far longer than pulling the gems from system gems.

Scenario:

== Rubygems ==
% gem list
Custom gem (0.1.0)

== Gemfile ==
source :gemcutter
gem "custom_gem"

Expected:

Installing Custom gem from system gems

Actual:

Fetching source index from http://gemcutter.org
Installing Custom gem from system gems

Incase newer gems are available in the source, but not system gems, have a --force option

Or inverse, add option not to pull source index unless needed, i.e. --skip-sources

@indirect
Copy link
Member

The option to not pull the source index unless needed already exists. You activate it with bundle lock. As long as your bundle is locked, and the gems in the lockfile are available locally, bundle install will not fetch the source index.

@KieranP
Copy link
Author

KieranP commented Feb 20, 2010

Ah, I see. Thanks.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants