Hi, You have a valid point. However, I believe the newer versions are a result of my not specifying all the dependencies in the Gemfile. As an example, I specified cucumber-rails ~> 0.3.0 and it picked up cucumber 1.0.2 which picked up gherkin 2.4.1. Before, the necessary versions as specified in the environment file were the ones picked up when doing 'rake gems:install RAILS_ENV=cucumber'. The way they're specified, I couldn't install the required set of gems.
One could argue that I could have just changed the environment files, and they would be right. However, it seemed more approrpriate to take the step to use bundler since it's on the tracks roadmap to migrate to rails 3, and rails 3 uses bundler. If it's preferrable, I can take the dependencies that bundler resolved and update the config.gem lines in the environment files to pull in those when 'rake gems:install' is ran. -- Matt On Mon, Aug 22, 2011 at 11:08 AM, Stefan Richter <[email protected]> wrote: > Hi, > > Although I am a huge fan of bundler, I am not too sure its necessary ASAP as > the old versions are not solved by bundler but by you specifying a different > version. The question for this move is more about the users and their > migration path. > > -stefan > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Matt Rogers > Sent: Monday, August 22, 2011 4:57 PM > To: Reinier Balt > Cc: [email protected] > Subject: [Tracks-discuss] Re: Bundler and Tracks > > Hi, > > I think we should do it sooner than 2.2, so ASAP, but I don't know what the > timeline is for 2.1. There are several reasons for that: > > 1. Remove a potential barrier to entry for contributors. A lot of the errors > I was getting were due to the fact that some things on my system were too new > (GCC 4.6, for example) and so the older versions of things that were > specified in the environment files wouldn't install because their native > extensions wouldn't compile. With bundler, we can pick up new enough versions > of gems so that they'll work but they're still compatible with some of the > older gems we need because we're still a Rails 2 app. > > I couldn't run the cucumber test suite at all until I finished this work. > > 2. Provides a consistent environment to use with development, testing, and > deployment w/o having to go through "rake gems:install" multiple times for > each environment. The gems in the Gemfile are grouped, so for a production > only build, you can tell the bundle command to exclude certain groups to get > a minimum amount of gems. > > 3. One step closer towards being on Rails 3. Bundler is baked in and used by > default. This is only a nice side effect due to the fact that I looked at the > roadmap in Assembla and saw Rails 3 on there. > > 4. Somebody's done the work, why not merge it? :) > > Thanks, > Matt > > > On Mon, Aug 22, 2011 at 2:47 AM, Reinier Balt <[email protected]> wrote: >> Sorry, didn't see it :-) >> >> I'd like to move to bundler for 2.2. Or do people think it would be >> best to do it asap? >> >> Reinier >> >>> -----Oorspronkelijk bericht----- >>> Van: [email protected] >>> [mailto:tracks-discuss- [email protected]] Namens Matt >>> Rogers >>> Verzonden: maandag 22 augustus 2011 4:43 >>> Aan: [email protected] >>> Onderwerp: [Tracks-discuss] Bundler and Tracks >>> >>> Hi, >>> >>> I've submitted a pull request (#5) for converting Tracks to use >>> Bundler instead of Rails 2.3.x default gem handling. >>> >>> I've successfully been able to run the unit tests and the cucumber >>> (w/o >>> selenium) tests, and more importantly, my use of the app over the >>> last few days has not hit any snags, so I feel pretty comfortable with it. >>> >>> Reinier, I didn't see your user id listed when I sent the pull >>> request, so >> I'm >>> going to assume you haven't seen it yet - which would be why I'm >>> sending this email :) >>> >>> Comments and feedback much appreciated! >>> >>> Thanks >>> -- >>> Matt >>> _______________________________________________ >>> Tracks-discuss mailing list >>> [email protected] >>> http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss >> >> > _______________________________________________ > Tracks-discuss mailing list > [email protected] > http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss > _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
