On Sat, Jun 11, 2011 at 6:07 AM, Brian Guthrie <[email protected]> wrote: > Hi Ketan - I've updated the 2.0 milestone on Github with the release > dates you've outlined. I've attempted an improvement at Bundler > support today, under the assumption that CC.rb itself needs to veer a > little bit outside of the mainstream; we're vendoring our .gem files, > and my assumption (which may be incorrect) is that most Ruby projects > aren't currently doing that. Even if they are, they'll need the > ability to turn --local off. > > So my proposed solution is a configurable array of bundler_args on > Project. It's not a thrilling solution; feels a bit like a compromise > to me - a little bit more manageable and idiomatic than a plain > string, a little less complex than trying to support full-on args > rewriting. Please, everyone, let me know if this won't work for you, > and particularly if you'd like to handle it a better way.
Maybe I missed bundler discussion on another thread, but why not just default to "bundle install" with no args, and allow a string to be passed to override args? Why do we need to pass any other args by default? _______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
