Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Aug 26, 2012
  1. @indirect

    inject command with specs

    indirect authored
  2. @indirect
Commits on Aug 25, 2012
  1. @hone

    Fix #2075. Return to old namespace behavior.

    hone authored
    $1 gets overidden by gsub.
Commits on Aug 20, 2012
  1. @jdelStrother

    Suggest alternatives when typoing gem names

    jdelStrother authored
    $ bundle open thinking_sphinx
    Could not find gem 'thinking_sphinx'.
    Did you mean thinking-sphinx?
Commits on Aug 16, 2012
  1. @indirect

    Merge pull request #2060 from jdelStrother/picky_update

    indirect authored
    Error-out on "bundle update unknown-gem"
  2. @indirect

    Merge pull request #2061 from gentoo/master

    indirect authored
    Simple fix for running specs as root.
Commits on Aug 14, 2012
  1. @hone
  2. @hone

    fix test case names

    hone authored
  3. @hone
  4. @Flameeyes

    spec: do not check for /usr/bin not to be writable when running as root.

    Flameeyes authored
    This test would fail on default Gentoo installs as the package is
    executed as root.
Commits on Aug 13, 2012
  1. @jdelStrother
Commits on Aug 9, 2012
  1. @hone
  2. @hone
Commits on Jul 17, 2012
  1. @hone

    don't need these tests in 1.2

    hone authored
  2. @hone

    Merge branch '1-1-stable'

    hone authored
  3. @hone

    special case `ruby` directive

    hone authored
    This is light of the upcoming 1.2.0 release which adds this feature.
    This way people still using 1.1.x can run 1.2.0 Gemfiles that employ
    this feature and get a notification about upgrading.
  4. @hone

    rename --no-lock to --dry-run

    hone authored
  5. @svenfuchs @hone

    Make locking the Gemfile optional on $ bundle check

    svenfuchs authored hone committed
    Currently `bundle check` locks the Gemfile. According to @indirect this
    behaviour is intentional (see!/indirect/status/186493694013210624).
    I am working on a CLI monitoring tool that makes it easier to work with
    cross-repository changes on projects that are split up into several
    This tool is supposed to display status information such as out-of-date
    bundler Gemfiles etc. To do so it watches the filesystem and queries for
    information on demand. Using `bundle check` to do so currently leads to
    highly confusing side-effects because suddenly the git working directory
    might be dirty - having changed the Gemfile.lock - because `bundle
    check` has been run in the background.
    This patch adds a boolean method option `--[no-]lock` to `bundle check`
    that defaults to `true` in order to not change the current behaviour but
    make it possible for users to turn it off.
    Sidenote: apparently the same behaviour also applies to `bundle show`.
    Am I the only one who finds this highly confusing?
  6. @hone
  7. @hone
  8. @josevalim

    Prune git and path directories inside vendor/cache, closes #1988

    josevalim authored
    From this commit on, we add a .bundlecache file inside
    each git/path directory in vendor/cache so we know it
    came from bundler. This allow us to delete those specific
    directories without messing with user's specific ones.
  9. @josevalim
Commits on Jul 13, 2012
  1. @hone

    loosen ruby directive for engines

    hone authored
    allow other engines to qualify when the engine is omitted. So, in the
    ruby "1.9.3"
    will work with JRuby and RBX as long as the RUBY_VERSION matches
Commits on Jun 22, 2012
  1. @postmodern
Commits on Jun 14, 2012
  1. @dlee @josevalim

    specs: check :branch for local overrides on runtime

    dlee authored josevalim committed
    Signed-off-by: José Valim <>
  2. @josevalim
Commits on Jun 13, 2012
  1. @indirect

    Merge remote-tracking branch 'rkh/optional-branch'

    indirect authored
  2. @phil-monroe
Commits on Jun 12, 2012
  1. @phil-monroe
Commits on Jun 7, 2012
  1. @indirect

    Merge pull request #1920 from drogus/gem_path_fix

    indirect authored
    Always try to keep original GEM_PATH
  2. @drogus

    Always try to keep original GEM_PATH

    drogus authored
    This fixes a problem which occures when you want to run `bundle` command
    inside code that already loads `Gemfile`. When you start a command with
    `bundle exec` it sets `RUBYOPT` to
    `-I$PATH_TO_BUNDLER -r"bundler/setup"`. Because of that, when you run
    the actual command it already requires bundler, which is fine, but since
    `GEM_PATH` was cleared on the first run `ORIGINAL_ENV` will include
    empty `GEM_PATH`. Now when you run `Bundler.with_clean_env`, you will
    not have any bundler specific env variables, but you will also not have
    original gem path, which will make it impossible to run any gem.
    To fix this I try to always keep a reference to original gem path, so
    it's not emptied along the way.
Commits on Jun 5, 2012
  1. @bowsersenior @hone

    Fix typos in error messages

    bowsersenior authored hone committed
Commits on Jun 4, 2012
  1. @bowsersenior
Commits on May 30, 2012
  1. @indirect
Commits on May 28, 2012
  1. @indirect

    Merge v1.1.4 from branch '1-1-stable'

    indirect authored
Something went wrong with that request. Please try again.