Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Feb 13, 2012
  1. @indirect
  2. @indirect

    handle Gemfile syntax errors

    indirect committed
  3. @indirect
  4. @indirect

    Merge pull request #1661 from koraktor/bundler

    indirect committed
    This was initially requested in #1527 and I did a first iteration of it back then.
    Today, I decided that this can still be improved, so I improved formatting and added a spec.
Commits on Feb 12, 2012
  1. @koraktor
  2. @koraktor
  3. @koraktor

    Added graceful handling of Gemfile syntax errors

    koraktor committed
    See issue #1527 for the initial request.
  4. @sferik

    Merge pull request #1660 from vijaydev/fix_path_warn

    sferik committed
    Fixes warning of variable shadowing
  5. @sferik

    Merge pull request #1658 from koraktor/fix-viz-deprecation-notices

    sferik committed
    Fixed deprecation warnings in `bundle viz`
  6. @vijaydev
  7. @koraktor

    Fixed deprecation warnings in `bundle viz`

    koraktor committed
    Newer versions of ruby-graphviz also warn about nil options.
    So I decided to clear out the :label option if it's nil.
Commits on Jan 28, 2012
  1. @sferik

    Merge pull request #1638 from knu/fix_brace_expansion

    sferik committed
    Reduce invocation of `git ls-files` and remove ksh/bash-ism.
Commits on Jan 27, 2012
  1. @dekellum @indirect

    Add simple cache to Bundler.load_gemspec

    dekellum committed with indirect
    In some projects, for example those with 10s of local gemspecs, use of
    `git ls-files` for spec.files, or specs requiring significant source
    to get at a spec.version; this change to cache load_gemspec results in
    notable performance gains.
    The cache also avoids loading these same gemspecs repeatedly with
    different LOAD_PATH values.
  2. @eric1234 @indirect

    Avoid passing RUBYOPT changes in with_clean_env block.

    eric1234 committed with indirect
    Restoring the original ENV generally restored the RUBYOPT changes, but certain
    use cases leak through. This commit ensures that the ENV is truely clean by
    always checking for RUBYOPT changes and zapping them if they do exist.
    This commit fixes #1604 (second attempt)
Commits on Jan 20, 2012
  1. @sferik

    Merge pull request #1637 from knu/gemspec_from_rakefile

    sferik committed
    Add Bundler::GemHelper.gemspec.
  2. @knu

    Reduce invocation of `git ls-files`.

    knu committed
    This also removes shell brace expasion which is a ksh/bash extension
    that does not work with POSIX sh.
  3. @knu
  4. @knu

    Add Bundler::GemHelper.gemspec.

    knu committed
    This method provides a way to access the Gem::Specification object
    generated from the gemspec file from within a Rakefile generated by
    `bundle gem'.
    You can keep DRY by using it to pull in attributes like `test_files',
    `extra_rdoc_files' and `extensions' for building tasks like `test',
    `rdoc' and `compile', respectively.
Commits on Jan 19, 2012
  1. Merge pull request #1625 from brixen/ruby-independent

    André Arko committed
    Use the same ruby to run subprocesses as is running rake.
Commits on Jan 16, 2012
  1. @sferik

    Merge pull request #1630 from invisiblefunnel/master

    sferik committed
    Typo fix in installer error message
  2. @invisiblefunnel
Commits on Jan 13, 2012
  1. @brixen

    Use the same ruby to run subprocesses as is running rake.

    brixen committed
    For implementations like Rubinius that can run from a source directory without
    installing and which do not overwrite gem binary wrappers in system
    directories, it is possible to invoke the Rakefile with eg 'rbx -S rake spec'
    while the system Ruby is on PATH as 'ruby' and 'gem'. This results in the
    system Ruby running the rake subprocesses instead of Rubinius as intended.
    These changes use Gem.ruby, which returns the path to the Ruby implementation
    running rake and use -S to search for the gem bin wrapper on PATH. Rubinius
    prepends distinguished directories when processing -S so that gems installed
    into Rubinius are found first.
    The explicit requiring of rubygems may be controversial. Evan said it was ok
    but the rest of the changes stand on their own if it's desirable to remove the
Commits on Dec 21, 2011
  1. @sferik

    Merge pull request #1598 from spastorino/1-1-stable

    sferik committed
    bundle exec shouldn't run Bundler.setup just setting the correct rubyopts options is enough
  2. @spastorino

    PERFORMANCE: bundle exec shouldn't run Bundler.setup just setting the…

    spastorino committed
    … right rubyopts options is enough
    This makes bundle exec rake environment of this Gemfile, 17% faster
Commits on Dec 20, 2011
  1. @sferik

    Fix typo in rake task description

    sferik committed
    Closes #1595.
Commits on Dec 14, 2011
  1. @hone


    hone committed
  2. @hone

    update changelog

    hone committed
  3. @hone


    hone committed
  4. @hone

    update changelog

    hone committed
  5. @hone

    Merge pull request #1588 from cowboyd/bundler

    hone committed
    The binstubs generated by Bundler currently require both rubygems and bundler to be installed in order to execute: requirements not guaranteed at runtime for a standalone bundle.
    This introduces a separate method to generate binstubs when generating a standalone bundle. It first adds the root of the standalone to the load path, and then requiring `bundler/setup` from there.
    I was on the fence whether to leave the load path alone and load bundler/setup.rb directly via its path relative to the generated executeable, but in the end decided to go the way I did so that application code requiring bundler/setup will continue to function.
    Im pretty excited about the standalone feature, and I hope that this makes it into 1.1
  6. @hone
Commits on Dec 13, 2011
  1. @cowboyd
  2. @cowboyd
Commits on Dec 12, 2011
  1. @sferik

    Merge pull request #1586 from hirochachacha/1213_rewrite_viz_graph

    sferik committed
    fix bundle viz command
  2. @cowboyd
Something went wrong with that request. Please try again.