Permalink
Switch branches/tags
Commits on Aug 28, 2012
  1. update version in readme

    indirect committed Aug 28, 2012
Commits on Aug 26, 2012
  1. inject command with specs

    indirect committed Aug 26, 2012
Commits on Aug 25, 2012
  1. Fix #2075. Return to old namespace behavior.

    hone committed Aug 25, 2012
    $1 gets overidden by gsub.
Commits on Aug 24, 2012
  1. Merge pull request #2077 from schneems/schneems/bundler-case

    indirect committed Aug 24, 2012
    upcase bundler
  2. upcase bundler

    schneems committed Aug 24, 2012
    keep the case of "Bundler" consistent.
Commits on Aug 21, 2012
  1. Merge pull request #2069 from jdelStrother/levenshtein

    indirect committed Aug 21, 2012
    Suggest alternatives when typoing gem names
Commits on Aug 20, 2012
  1. Suggest alternatives when typoing gem names

    jdelStrother committed Aug 13, 2012
    eg
    $ bundle open thinking_sphinx
    Could not find gem 'thinking_sphinx'.
    Did you mean thinking-sphinx?
Commits on Aug 16, 2012
  1. Merge pull request #2060 from jdelStrother/picky_update

    indirect committed Aug 16, 2012
    Error-out on "bundle update unknown-gem"
  2. Merge pull request #2061 from gentoo/master

    indirect committed Aug 16, 2012
    Simple fix for running specs as root.
  3. Revert "Ruby 2.0 (trunk ruby) is not Ruby 1.9"

    indirect committed Aug 16, 2012
    As discussed in #1539 and #2056, Bundler uses platforms to distinguish Ruby ABI versions. That means the known (and ATM supported) use cases for the ruby_19 platform include Ruby 2.0.
    
    This reverts commit dcfb640.
Commits on Aug 14, 2012
  1. fix test case names

    hone committed Aug 14, 2012
  2. spec: do not check for /usr/bin not to be writable when running as root.

    Flameeyes committed Aug 14, 2012
    This test would fail on default Gentoo installs as the package is
    executed as root.
Commits on Aug 13, 2012
Commits on Aug 9, 2012
  1. Version 1.2.0.rc.2 and changelog

    hone committed Aug 9, 2012
Commits on Aug 7, 2012
  1. Merge pull request #1931 from coding46/patch-1

    radar committed Aug 7, 2012
    Simple Typo
Commits on Jul 18, 2012
  1. Fix 'LICENSCE' typo in CHANGELOG

    radar committed Jul 18, 2012
Commits on Jul 17, 2012
  1. Version 1.2.0.rc with changelog

    hone committed Jul 17, 2012
  2. don't need these tests in 1.2

    hone committed Jul 17, 2012
  3. Merge branch '1-1-stable'

    hone committed Jul 17, 2012
    Conflicts:
    	CHANGELOG.md
    	lib/bundler/dsl.rb
    	lib/bundler/version.rb
  4. Version 1.1.5 with changelog

    hone committed Jul 17, 2012
  5. special case `ruby` directive

    hone committed Jul 17, 2012
    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.
  6. rename --no-lock to --dry-run

    hone committed Jul 17, 2012
  7. Make locking the Gemfile optional on $ bundle check

    Sven Fuchs committed with hone Apr 1, 2012
    Currently `bundle check` locks the Gemfile. According to @indirect this
    behaviour is intentional (see
    https://twitter.com/#!/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
    repositories.
    
    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?