From: Xavier Noria <fxn@...>
Date: 2010-05-19T02:54:46+09:00
Subject: Re: Bundler Groups

On Tue, May 18, 2010 at 7:39 PM, Intransition <transfire@gmail.com> wrote:

> I see. So ActiveRecord's tests are designed to test against these
> three databases. How are the other adapters tested?

The rest of adapters have their own projects. Rails core is not tested
against Oracle, say.

> Also shouldn't
> this be part of ActiveRecord's Gemfile?

There's only one Gemfile in Rails.

> And what if you have only one
> of these databases on your system, or perhaps I am only concerned with
> an issue in the mysql adapter. That would indicate a need to select
> among them.

One should not submit a patch or touch the core without first running
the test suite. Technically you can still comment the line of the
Gemfile that requires the Postgres driver, but you get some vinegar
there :).

> And that makes me wonder how these group selections filter down to
> their dependencies. I take it the --without selections applies to all
> of them?

The dependency graph is computed against everything no matter what.
That's why even if you do not install something because of --without,
bundler will fetch (but not install) the gem. Goal is to compute a gem
set that is consistent across environments.

> I can see that. But it doesn't seem like a strong case. I mean, is it
> worth remembering this group just to avoid these two dependencies b/c
> you only plan to be doing doc work? Might it not just have a mode to
> ask you which dependencies you want?

It is a feature you of course can ignore. It is there because the use
cases where considered important enough to have it implemented.