Bundler update and fixes to solve Bundler dependencies
jstribny at redhat.com
Wed Nov 12 14:25:53 UTC 2014
today I updated Bundler to the latest 1.7.6 version and fixed an issue with Bundler's
dependencies. Although you probably didn't come across this, the issue showed up during
packaging Vagrant which uses Bundler underneath.
As you may know Bundler actually vendors its dependencies (thor and net-http-persistent)
in lib/bundler/vendor, but those were removed in Fedora. The problem arises when you make
Bundler to lock the dependencies with Bundler.setup which means that Bundler clears out
$LOAD_PATH keeping itself on the path, but without its dependencies. When the dependency
is requested to be loaded, Bundler just adds the vendor dir on $LOAD_PATH. On Fedora
however the vendor dir is empty and therefore Bundler cannot continue (unless the
requested vendored library has been previously loaded into memory).
The most reasonable fix was to go with symlinks to system RubyGems that are also specified
as runtime dependencies (although missing in gemspec). The symlinks are generated after
Bundler installation or upon removal of old Bundler's dependencies (so to say on their
update, but after the old files are removed). This way Bundler works a little bit more
like its upstream counterpart and doesn't break anymore.
If you can, please help me to test it and let me know what you think.
 in rawhide, builds for f21 and f20 are in updates-testing
More information about the ruby-sig