Remember alternative Gemfile

[coilysiren]

From @ineiti on May 14, 2015 5:12

When I use an alternative Gemfile like

bundle install --gemfile Gemfile.dev

I'd like the Gemfile.dev.lock be used in any require 'bundler/setup'

Usecase:

for my development, I like having path: in the Gemfile, but not for deployment. So I made a second Gemfile and I am trying to use that one, but it always takes the gems from Gemfile.lock

Copied from original issue: rubygems/bundler-features#86

[coilysiren]

From @segiddins on May 14, 2015 5:14

You can use the BUNDLER_GEMFILE environment variable to this effect

[coilysiren]

From @ineiti on May 14, 2015 7:0

OK - that might work. But I still it would be more logical to continue the way of #3320 and also use the config:gemfile for bundler/setup.

[coilysiren]

From @ineiti on May 14, 2015 7:30

Now a step further. If I do first

bundle config --local gemfile Gemfile.dev

everything works as expected. But one might wonder whether the --gemfile option in bundle install shouldn't set that configuration by itself.

[coilysiren]

From @asymmetric on July 2, 2015 19:14

@ineiti, according to this issue:

In Bundler 2.0, flags passed to commands will no longer be remembered, and instead should be set using bundle config if they should apply to every run

[segiddins]

I think we can close this -- it won't apply in bundler 2 since no flags will be remembered, and the likelihood of us fixing it for a final 1.x release is looking exceedingly small

[segiddins]

Closing for the reasons stated above.