If you change the gemspec in a git repos, gem bundle --update doesn't notice it because the git clone isn't updated.

This changes the git source to clone the repos if the checkout is missing and to fetch origin if present. In both cases, the desired ref is checked out. Thus gem bundle --update ensures the git branch and its gemspec are up-to-date.

http://github.com/jeremy/bundler/commit/155e2f09658e1b4f8ac8e1f4e15a1b02e92a6dee

Due to use of Symbol#to_proc: keys = %w(vendored_at path only except git path bundle require_as tag branch ref).map(&:to_sym)

dsl.rb:85

I noticed a problem that comes up with some gems such as after_commit. I posted a gist here with the details: https://gist.github.com/039d9e5ce54f4a11ce70. It seems like some gems when loaded assume that Rails has already been loaded... in the case of after_commit it tries to include a module in all the subclasses of ActiveRecord::ConnectionAdapters::AbstractAdapter; however, since gem bundler loads the after_commit.rb library before Rails has figured out which subclasses of AbstractAdapter to initialize (MysqlAdapter in my case), the module is not included and breaks my app.

I can't figure out if this is a problem with gem bundler for changing gem load order... or a problem with a bunch of gems out there that /assume/ a certain load order. In any case it seems like the community needs to agree on how to go about Rails gem development.

ERROR: While executing gem ... (TypeError)

wrong argument type Pathname (expected String)

The problem is reproducable for any gem that wants to install binaries (rake, rails, ...)

The solution:

diff --git a/lib/bundler/repository.rb b/lib/bundler/repository.rb
index 418ecbb..6333f6f 100644
--- a/lib/bundler/repository.rb
+++ b/lib/bundler/repository.rb
@@ -130,7 +130,7 @@ module Bundler
         installer = Gem::Installer.allocate
         installer.instance_eval do
           @spec     = spec
-          @bin_dir  = bin_dir
+          @bin_dir  = bin_dir.to_s
           @gem_dir  = path.join("gems", "#{spec.full_name}")
           @gem_home = path
           @wrappers = true

The problem is jruby only accepts strings as argument of Dir.mkdir, while MRI will accept anything it can convert to a String. Bundler uses a Pathname object for the bin dir.

Give an invalid vendored_at path and gem bundle will give you an error saying the gemspec's require_lib is bad, when really the path to it is

http://github.com/jeremy/bundler/commit/1ee81efd8822dd5776df9630b0eb086983ad1cdc
http://github.com/jeremy/bundler/commit/eba16636e86c54a3a0118aa6b0113453bc49e359

ENV vars such as ARCHFLAGS

In a deploy scenario, it would be nice to be able to symlink vendor/gems to a shared location.

These should be relative links

I have had issues with bundler when using it on a windows machine. I initially thought it was because of spaces in the directory path but then when trying it on a location without spaces, it still had problems. If I try to install do_sqlite3 using gem install it works but if I try to install it using gem bundle, it doesn't. A cli session showing this is at http://pastie.org/687220

Also, pasted at http://pastie.org/687233 is Luis Lavena's response to this when I submitted it to him on the rubyinstaller mailing list

Hi,
I'm trying to use Bundler in my project but I'm still getting the following error message:

root@ROOT:/c/dev/MUNI/Bakalarka/portfonica$ ruby script/server webrick
=> Booting WEBrick
=> Rails 2.3.4 application starting on http://0.0.0.0:3000
c:/dev/MUNI/Bakalarka/portfonica/gems/environment.rb:157:in `instance_eval': can't convert Symbol into Integer (TypeError)
        from c:/dev/MUNI/Bakalarka/portfonica/gems/environment.rb:131:in `gem'
        from (eval):10:in `require_env'
        from c:/dev/MUNI/Bakalarka/portfonica/gems/environment.rb:157:in `instance_eval'
        from c:/dev/MUNI/Bakalarka/portfonica/gems/environment.rb:157:in `require_env'
        from c:/dev/MUNI/Bakalarka/portfonica/config/../config/preinitializer.rb:16:in `block (2 levels) in extend_environment'
        from c:/dev/MUNI/Bakalarka/portfonica/gems/gems/rails-2.3.4/lib/initializer.rb:137:in `process'
        from c:/dev/MUNI/Bakalarka/portfonica/gems/gems/rails-2.3.4/lib/initializer.rb:113:in `run'
        from c:/dev/MUNI/Bakalarka/portfonica/config/environment.rb:5:in `'
        from c:/dev/MUNI/Bakalarka/portfonica/gems/gems/activesupport-2.3.4/lib/active_support/dependencies.rb:156:in `require'
        from c:/dev/MUNI/Bakalarka/portfonica/gems/gems/activesupport-2.3.4/lib/active_support/dependencies.rb:156:in `block in require'
        from c:/dev/MUNI/Bakalarka/portfonica/gems/gems/activesupport-2.3.4/lib/active_support/dependencies.rb:521:in `new_constants_in'
        from c:/dev/MUNI/Bakalarka/portfonica/gems/gems/activesupport-2.3.4/lib/active_support/dependencies.rb:156:in `require'
        from c:/dev/MUNI/Bakalarka/portfonica/gems/gems/rails-2.3.4/lib/commands/server.rb:84:in `'
        from script/server:3:in `require'
        from script/server:3:in `'

I just generated a empty rails project and followed this steps:

• run gem install bundle command
• create a Gemfile in the root folder inside the empty rails project
• edit the one (a contain of this file is below)
• create config/preinitializer.rb file
• put a code for this file from http://is.gd/4MmDN
• run the command gem bundle

Gemfile

clear_sources
source 'http://gemcutter.org'

bundle_path 'gems'

gem 'rails',     '2.3.4'
gem 'haml',      '2.2.10'
gem 'prawn',     '0.5.1'
gem 'couchrest', '0.33'

only :test do
  gem 'rspec',       '1.2.9'
  gem 'rspec-rails', '1.2.9'
end

Now you need to run ruby script/server. You should get the error message above.

I tried to use disable_system_gems and without one in the Gemfile but without any success.

I've added support for shallow git clones which reduces the size of the repository.

The test is not the nicest but git doesn't do shallow clones on file:// repos...

See http://github.com/jweiss/bundler/commit/81869330f4442a5630c62d080ee395d205fb2179

Maybe vendor/gems/repos ?

I've been thinking more about the 'circular symlink' thing and I think the approach is desirable even though the symlink isn't. (regarding http://github.com/wycats/bundler/issues/closed#issue/64)

Say you don't do the circular approach:

[sample.gemspec]
Gem::Specification.new do |s|
  s.name = "sample"
  s.version = "1.0"
  s.add_dependency "rack", "= 1.0.0"
end

[Gemfile]
spec = eval File.read("sample.gemspec")
spec.dependencies.each do |dep|
  options = {}
  options[:only] = :testing if dep.type == :development

  gem dep.name, dep.version_requirements, options
end

When you bundle this your environment.rb file looks like this:

[vendor/gems/environment.rb]
...
$LOAD_PATH.unshift File.expand_path("#{dir}/gems/rack-1.0.0/bin")
$LOAD_PATH.unshift File.expand_path("#{dir}/gems/rack-1.0.0/lib")

...
@bundled_specs["rack"] = eval(File.read("#{dir}/specifications/rack-1.0.0.gemspec"))
@bundled_specs["rack"].loaded_from = "#{dir}/specifications/rack-1.0.0.gemspec"

What's missing is are the lib and bin paths for the working directory (ie for the sample project). This prevents you from using the environment.rb file to setup your full environment; at some point you need to add whatever local load paths you need.

Instead you could go the route of depending on yourself, which isn't as circular as it sounds because you're really just making an environment.rb that includes the local load paths... there's actually nothing circular going on.

[Gemfile]
spec = eval File.read("sample.gemspec")
gem spec.name, spec.version

Produces:

[vendor/gems/environment.rb]
...
$LOAD_PATH.unshift File.expand_path("#{dir}/../../bin")
$LOAD_PATH.unshift File.expand_path("#{dir}/../../lib")
$LOAD_PATH.unshift File.expand_path("#{dir}/gems/rack-1.0.0/bin")
$LOAD_PATH.unshift File.expand_path("#{dir}/gems/rack-1.0.0/lib")

...
@bundled_specs["sample"] = eval(File.read("#{dir}/specifications/sample-1.0.gemspec"))
@bundled_specs["sample"].loaded_from = "#{dir}/specifications/sample-1.0.gemspec"
@bundled_specs["rack"] = eval(File.read("#{dir}/specifications/rack-1.0.0.gemspec"))
@bundled_specs["rack"].loaded_from = "#{dir}/specifications/rack-1.0.0.gemspec"

Now you can use a test task like this:

[Rakefile]
task :test do
  test = Dir.glob('test/**/*_test.rb')
  cmd = ['ruby', '-w', '-rvendor/gems/environment.rb', '-e', 'ARGV.dup.each {|test| load test}'] + tests
  system(*cmd)
end

In this setup the entirety of your environment is handled by your gemspec + bundler, which I think is not only slick but adds to the completeness of the sandbox.

Again the only practical issue of this approach is the circular symlink which messes up text editors. A check can prevent the creation of the symlink. Omitting the symlink doesn't appear to break anything because it isn't actually used in the environment.rb file. The patch is here for your consideration: bahuvrihi@3731b5a

To solve this problem:

json, json_pure and yajl-ruby all get downloaded and required through the resolution process.

I would like to specify that I'd like to use yajl while excluding json and json_pure.

I'm trying to use bundler with disable_rubygems while still using Bundle::Environment.load to do all my require's. Would it be possible to open up a hook into bundler where I could just require "bundler/environment" and not pick up the rubygem core class requirements (like remote_fetcher, etc)?

Preinitializer example with bundler for Rails 2.3 does not use require_dependency neither loads init.rb files. Something along those lines might fix it:

require "#{File.dirname(__FILE__)}/../vendor/bundler_gems/environment"

Gem.loaded_specs.values.each do |spec|
  require_dependency File.expand_path("lib", spec.full_gem_path)
  init = File.expand_path("init", spec.full_gem_path)
  require init if File.exists?(init)
end

Thanks Carlhuda! :)

Minor suggestion:

Was banging my head against the wall the other day when gems installed locally weren't being installed via "gem bundle" command. Turns out I had disable_system_gems on. I know, dumb error, but it would be nice if it gave a more detailed warning after it cant find a gem of where it tried to look.

Hi,

I noticed that with Hpricot 0.8.2 (which is available for both MRI and JRuby), running "gem bundle" with JRuby does not resolve the JRuby version of the gem. It just goes for the MRI version which fails due to native extensions.

jruby -S gem install hpricot --version 0.8.2

Installs the JRuby version, so I expected bundler to bundle the JRuby version as well.

Can anyone verify or recommend a fix?

Sometimes you submit your gem files to a file sharing service, it will be good if bundler will be able to download that gems and build them, without to create a remote gem repository.

    gem "gizmo_api", :url => 'http://example.com/files/gems/gizmo_api-1.2.3.gem'

I'd like to use bundler's great gem management system to make sure my desired gems are installed on my system. I have multiple projects using the same set of gems, and don't really want to have to vendor all of them separately. I'd like to be able to configure bundler to instal the gems onto my system, instead of vendoring them.

I believe I can get around this by setting my gem path to ~/.gem, and the configuration option may be to just use that setting in a system-specific manner.

My use-case is I'm working on a set of projects that just use ruby for some helpers (in particular Rake). I have a set of gems I'm using between these projects (in particular to manage some configuration variables), and I don't need the robustness of vendored gems (since they won't go to prod), but I do want to leverage the convenience of a Gemfile.

My comments on Corey's post:

Rails is still using GemInstaller to bootstrap itself and autoupdate rubygems. That's kinda silly, but still required to be called my automated CI box setup scripts (which are still languishing in my branch while I reconsider the approach...)

There should be something like this in bundler itself - like a shell script that you can wget and install with a one-liner. e.g.:

wget -O /tmp/bootstrap_bundler.sh http://github.com/wycats/bundler/raw/master/ci/bootstrap_bundler.sh && sh /tmp/bootstrap_bundler.sh

[ davidlee /tmp/wtf ]  # cat Gemfile 
disable_system_gems

gem 'mongo'

source 'http://gemcutter.org'
source 'http://gems.rubyforge.org'
source 'http://gems.github.com'

[ davidlee /tmp/wtf ]  # cat init.rb
require './vendor/gems/environment'
Bundler.require_env

[ davidlee /tmp/wtf ]  # ruby init.rb 
/private/tmp/wtf/vendor/gems/gems/mongo-0.18/lib/mongo/types/objectid.rb:130:in `require': uninitialized constant Mongo::InvalidStringEncoding (NameError)
    from /private/tmp/wtf/vendor/gems/gems/mongo-0.18/lib/mongo/types/objectid.rb:130:in `'
    from /private/tmp/wtf/vendor/gems/gems/mongo-0.18/lib/mongo/types/objectid.rb:24:in `'
    from /private/tmp/wtf/vendor/gems/gems/mongo-0.18/lib/mongo/types/objectid.rb:21:in `'
    from /private/tmp/wtf/vendor/gems/gems/mongo-0.18/lib/mongo.rb:6:in `require'
    from /private/tmp/wtf/vendor/gems/gems/mongo-0.18/lib/mongo.rb:6:in `'
    from /private/tmp/wtf/vendor/gems/environment.rb:80:in `require'
    from /private/tmp/wtf/vendor/gems/environment.rb:80:in `gem'
    from /private/tmp/wtf/vendor/gems/../../Gemfile:3:in `require_env'
    from /private/tmp/wtf/vendor/gems/environment.rb:102:in `instance_eval'
    from /private/tmp/wtf/vendor/gems/environment.rb:102:in `require_env'
    from init.rb:2:in `'

[ davidlee /tmp/wtf ]  # irb
ruby-1.9.1-p243 > require 'mongo'
 => true 
ruby-1.9.1-p243 > ^D%

Hi,

I lock in my versions in the Gemfile and sometimes I just want to pull in the latest and test against them. Would it make sense to have something like;

gem bundle --ignore-version(s)

which would pull in whatever the latest versions are for each gems so you can test against them and then decide whether or not to keep them. Obviously I can edit my Gemfile and take out the specified versions and git checkout if I don't want the change, but that gets annoying after changing a few. Im wondering if this might at all be useful for other people.

Cheers,

Dylan.

• *.gem downloading
• source index downloading

Downloading rack-test-0.5.3.gem
Downloading rake-0.8.7.gem
Downloading sqlite3-ruby-1.2.5.gem
Installing abstract (1.0.0)
C:/Ruby19/lib/ruby/gems/1.9.1/gems/bundler-0.7.1/lib/bundler/repository.rb:170:in `symlink': symlink() function is unimplemented on this mac
hine (NotImplementedError)

    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/bundler-0.7.1/lib/bundler/repository.rb:170:in `expand_vendored_gem'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/bundler-0.7.1/lib/bundler/repository.rb:121:in `block in do_install'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/bundler-0.7.1/lib/bundler/repository.rb:111:in `each'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/bundler-0.7.1/lib/bundler/repository.rb:111:in `do_install'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/bundler-0.7.1/lib/bundler/repository.rb:44:in `install'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/bundler-0.7.1/lib/bundler/environment.rb:60:in `install'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/bundler-0.7.1/lib/bundler/cli.rb:39:in `bundle'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/bundler-0.7.1/lib/bundler/cli.rb:65:in `run'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/bundler-0.7.1/lib/bundler/cli.rb:6:in `run'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/bundler-0.7.1/lib/bundler/commands/bundle_command.rb:68:in `execute'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command.rb:257:in `invoke'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:132:in `process_args'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/command_manager.rb:102:in `run'
    from C:/Ruby19/lib/ruby/gems/1.9.1/gems/rubygems-update-1.3.5/lib/rubygems/gem_runner.rb:58:in `run'
    from C:/Ruby19/bin/gem:21:in `<main>'

The context class created in environment.rb raises some warnings due to the @only and @except variables not being initialized. Example:

% echo 'gem "rack"' > Gemfile
% gem bundle
% ruby -w -rvendor/gems/environment -e 'Bundler.require_env(:test)'
./vendor/gems/environment.rb:72: warning: instance variable @only not initialized
./vendor/gems/environment.rb:78: warning: instance variable @except not initialized

The fix is to initialize the variables: bahuvrihi@b388d72 (note you may just want to cherry pick this commit -- it's off of a branch relating to another issue that hasn't been acted on yet -- http://github.com/wycats/bundler/issues#issue/72).

I just spent most of the day getting a Rails 2.3.5 project bundling cleanly on both 1.8.7 and 1.9.1.
In the end, I wound up with a working setup for both, but under 1.9.1 numerous warnings are printed as RubyGems constants are re-initialized.
One possible fix is the (trivial) attached patch, which simply doesn't require 'rubygems' in environment.rb if the 'gem' method is already defined.
Patch can be found here:
http://supremetyrant.com/ruby/bundler_rubygems_19.patch

I have the following in my Gemfile:

gem 'rails', '2.3.4', :path => 'vendor/rails'

When i run gem bundle, bundler downloads 2.3.5. If I leave off the :path option, it downloads the correct version.

i was getting this error - maybe this is a ruby 1.8.6 issue?

[dc@tetris:dev/fish]$ gem bundle --backtrace
ERROR: While executing gem ... (TypeError)

wrong argument type Symbol (expected Proc)
/Library/Ruby/Gems/1.8/gems/bundler-0.7.2/lib/bundler/dsl.rb:110:in `gem'
/Users/dc/dev/fish/Gemfile:8:in `evaluate'
/Library/Ruby/Gems/1.8/gems/bundler-0.7.2/lib/bundler/dsl.rb:14:in `load_gemfile'
/Library/Ruby/Gems/1.8/gems/bundler-0.7.2/lib/bundler/cli.rb:35:in `initialize'
/Library/Ruby/Gems/1.8/gems/bundler-0.7.2/lib/bundler/cli.rb:6:in `new'
/Library/Ruby/Gems/1.8/gems/bundler-0.7.2/lib/bundler/cli.rb:6:in `run'
/Library/Ruby/Gems/1.8/gems/bundler-0.7.2/lib/bundler/commands/bundle_command.rb:68:in `execute'
/Library/Ruby/Site/1.8/rubygems/command.rb:257:in `invoke'
/Library/Ruby/Site/1.8/rubygems/command_manager.rb:132:in `process_args'
/Library/Ruby/Site/1.8/rubygems/command_manager.rb:102:in `run'
/Library/Ruby/Site/1.8/rubygems/gem_runner.rb:58:in `run'
/usr/bin/gem:21

the following hack fixes it:

  # keys = %w(vendored_at path only except git path bundle require_as tag branch ref).map(&:to_sym)
  keys = [:vendored_at, :path, :only, :except, :git, :path, :bundle, :require_as, :tag, :branch, :ref]