Generated .bundle/environment.rb does not disable system gems. about bundler

[alg]

Was that an intention? I mean locking gem versions is one thing, and hiding everything else is completely different. It may be useful to show problems with implicit use of some gems, though.

[rubiii]

same here. system gems seem to be needed?!?

[carllerche]

If a system gem is needed, it should be added to the Gemfile. It's the only way to get a 100% repeatable environment.

[rubiii]

all gems are added to the gemfile. but they're still specified in environment.rb (rails 2.3.5). maybe that's not required anymore? will have to try this out later.

[alg]

@carllerche, there's a discussion (http://github.com/carlhuda/bundler/issues#issue/18) of how some gems can't be built on remote environments and should be used from the system collection. I tend to agree that building of mysql gem on different environments, for example, will require different set of keys that you won't be able to supply through Gemfile. On top of that, there will be proprietary gems that aren't in public repositories.

Bottom line, I wouldn't be so strict about hiding the system environment.