carlhuda/bundler — pull request #2182 by grosser (2012-11-24 06:54:41+00:00)
Title: an idea how to solve 95% of bundler complaining about stuff fixes #1994

most of the time bundler is annoying is when someone else on the team updated some dependency or I switched ruby, so how about being nice and just try to bundle before declaring failure.

Either `TRY_TO_BUNDLE=1 bundle exec foo` or `bundle do foo`

this is pretty crappy code, atm it fails after the bundling because the old dependencies are still cached, but should be fixable, I basically want to know if this is something that would get merged at all <-> if it's going in the right direction...

```
bundle do ruby -e 'puts 1'
trying to bundle ...
Fetching gem metadata from http://rubygems.org/..
Installing rake (0.9.5)
Using bundler (1.3.0.pre)
Your bundle is complete! Use `bundle show [gemname]` to see where a bundled gem is installed.
/Users/mgrosser/.rvm/gems/ruby-1.9.3-p327/gems/bundler-1.3.0.pre/lib/bundler/spec_set.rb:90:in `block in materialize': Could not find rake-0.9.5 in any of the sources (Bundler::GemNotFound)
```

/cc @rohit