Katello/katello — pull request #1096 by lzap (2012-11-20 13:07:16+00:00)
Title: Introducing bundler_ext rubygem

Here it is, we are getting rid of Bundler for production.

This patch requires bundler_ext rubygem and in production we are renaming Gemfile to Gemfile.in. Bundler is not used and bundler_ext is loading this file using system requires instead. We no longer need to delete Gemfile.lock too, because it is not being created.

We also no longer need to "cut" Gemfile, because bundler_ext loads only default gem group, using environment variable in the /etc/sysconfig/katello it is possible to load other groups, therefore it is possible to use bundler_ext also for development. All dependencies are loaded properly from RPMs.

I had to change few lines in the Gemfile and add :require statement, because bundler_ext is not able to determine requires from gem name for all of the gems.

Additional improvement is possibilty to put bundler_ext into non-strict mode. In this mode, katello will NOT fail if one or few dependencies was not resolved (loaded). This was blocking our installation process many times (because rake db:migrate failed). Now Katello will install more often and if we mess up a dependency, it will only break the part that require it (and not whole system). This can be easily switched off.

DO NOT MERGE

I am still waiting for: https://github.com/aeolus-incubator/bundler_ext/pull/3
and for: https://bugzilla.redhat.com/show_bug.cgi?id=878421