We may be in a position to apply the '--local' arg to bundler by checking existence of vendor/cache directory.
Ketan studios.thoughtworks.com | twitter.com/ketanpkr 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. > > Brian > > On Sat, Jun 11, 2011 at 4:39 AM, Ketan Padegaonkar > <[email protected]> wrote: >> On Jun 8, 2011 6:42 PM, "Brian Guthrie" <[email protected]> wrote: >>> If that's more appropriately tagged as 1.5, I think that's a >>> worthwhile conversation; I picked 2.0 because I figured enough time >>> had passed, and the structural changes were significant enough. >>> There's also some "future release" stuff lumped under 2.1. If you'd >>> like to add a release date to those milestones, which I haven't done >>> yet, I think that would be great. >> >> Calling this a 2.0 sounds good to me given that its been a while and >> its been a lot of improvements. >> >>> The release dates you've suggested sound reasonable to me. I think the >>> 17th is about as aggressive as I'm willing to go, though, I think. >>> >>> There are more improvements I'd like to see to Bundler support, >>> including on that I think needs to happen prior to the release >>> (arguments need to be properly configurable, for one). I have some >>> local changes here that I'll push up soon. >> >> Theres quite a few improvements that could be made. I'm thinking >> things like paths to ruby, rake bundler etc. I'm not sure if we can >> push all this into master without pushing the timeframe up ahead by a >> couple of weeks which I understand, and am fine with. >> >>> We still need proper Windows support. As far as I can tell, there's no >>> good way to get Nokogiri running there, so I'm planning on removing >>> that dependency. >> >> Rexml is a good alternative to nokogiri, it's not all that fast, but >> we're not doing a lot of XML parsing. So we should be good in that >> regard. >> >> - Ketan >> studios.thoughtworks.com | eclipse.org/swtbot | @ketanpkr >> _______________________________________________ >> Cruisecontrolrb-developers mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers >> > _______________________________________________ > Cruisecontrolrb-developers mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers > _______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
