Permalink
Commits on Aug 28, 2016
  1. @homu

    Auto merge of #4923 - bundler:seg-apple-git-support, r=indirect

    [Env] Support running `bundle env` when not inside a bundle
    homu committed Aug 28, 2016
Commits on Aug 26, 2016
  1. @segiddins

    [Env] Support running `bundle env` when not inside a bundle

    segiddins committed Aug 26, 2016
  2. @homu

    Auto merge of #4491 - bundler:seg-exec-file--zsh, r=indirect

    [Exec] Add specs for $0 and __FILE__ when loaded
    
    Tests for #4488
    homu committed Aug 26, 2016
Commits on Aug 25, 2016
  1. @homu

    Auto merge of #4836 - bundler:seg-resolve-for-specific-platforms, r=i…

    …ndirect
    
    Resolve for specific platforms
    
    Closes #4295.
    
    This will require adding a bunch of tests, as well as figuring out how to put this new behavior behind a feature flag (thus fixing all of the existing tests).
    homu committed Aug 25, 2016
  2. @segiddins

    [Plugin] Don’t print GemfileErrors twice

    segiddins committed Aug 18, 2016
  3. @segiddins

    [Definition] Validate platform in addition to ruby

    # Conflicts:
    #	lib/bundler/cli/doctor.rb
    segiddins committed Aug 18, 2016
  4. @segiddins
  5. @segiddins
  6. @segiddins
  7. @segiddins
  8. @segiddins
  9. @segiddins
  10. @segiddins
  11. @segiddins
  12. @segiddins
  13. @segiddins
  14. @segiddins

    [LazySpecification] Only materialize for the current platform when

    :specific_platform is enabled
    segiddins committed Aug 5, 2016
  15. @segiddins
  16. @homu

    Auto merge of #4654 - bundler:aa-ruby-version-conflict-message, r=ind…

    …irect
    
    Add resolver-style error messages for required Ruby conflicts
    
    *Proposal:* When a gem in the Gemfile requires a Ruby version different than the Gemfile's `ruby`, print a conflict error message that looks more or less exactly like any other resolution conflict error.
    
    *Current behavior:* On `master` today, Bundler will ignore the gem's required_ruby_version until install-time, and raise an exception like "require_ruby-1.0 requires ruby version > 9000, which is incompatible with the current version`.
    
    After #4650 has been merged, Bundler will correctly reject gems that require a different version of Ruby, and instead print the error "Could not find `required_ruby` in any of the sources in your Gemfile".
    
    *Rationale for change:* I believe that error message is surprising and misleading. The source _does_ contain `required ruby`, and I think we'll get bug reports about how our error message is wrong.
    homu committed Aug 25, 2016
Commits on Aug 24, 2016
  1. @homu

    Auto merge of #4898 - JuanitoFatas:feature/generated-readme-github-ur…

    …l, r=segiddins
    
    Fill in git username to the generated gem's contributing section of README.md
    
    This Pull Request changes the GitHub URL in the Contributing section of README.md from generated gem (e.g. `bundle gem foo`).
    
    Why:
    
    I found myself change `[USERNAME]` to my git username so many times and I also help [some](https://github.com/suzuki86/rhymer/pull/1/files) [people](https://github.com/fastly/blockbuster/pull/12/files) [fix](https://github.com/abookyun/taiwan_validator/pull/2/files) [this](https://github.com/mkhairi/materialize-sass/pull/62/files).
    
    So I think this should be filled when new gem is generated. When git username not set, falls back to `[USERNAME]`.
    
    I don't really know how to make tests DRY, please advise, thank you.
    homu committed Aug 24, 2016
  2. @homu

    Auto merge of #4624 - chrismo:openssl_version_in_bundle_env, r=segiddins

    Add OpenSSL::OPENSSL_VERSION to `bundle env`
    homu committed Aug 24, 2016
Commits on Aug 23, 2016
  1. @segiddins

    [Exec] Add specs for $0 and __FILE__ when loaded

    segiddins committed Apr 30, 2016
  2. @segiddins

    Update resolving specs for required ruby version refactor

    segiddins committed Aug 23, 2016
  3. @homu

    Auto merge of #4878 - Zorbash:binstubs-standalone-flag, r=segiddins

    Change standalone flag of binstubs cmd to boolean
    
    This flag was introduced in #4610, declared with the same code as the flag found in the `install` command.
    
    In the case of the `install` command, it makes sense to be an `Array` option, since
    one can specify groups.
    
    This doesn't hold true for the `binstubs` cmd where `--standalone` just stands to signify
    whether the generated stubs will require the Bundler runtime or not.
    
    In the current implementation even passing groups with the flag doesn't have any affect.
    homu committed Aug 23, 2016
  4. @segiddins

    [Resolver] Remove ruby_version attribute

    segiddins committed Aug 23, 2016
  5. @segiddins
  6. @segiddins
  7. @segiddins
  8. @segiddins
  9. @segiddins
  10. @segiddins
  11. @segiddins
  12. @indirect @segiddins
  13. @homu

    Auto merge of #4908 - okkez:add-missing-respond_to_missing, r=segiddins

    Add missing definition of `respond_to_missing?`
    
    Because we should overwrite this method when we overwrite
    `method_missing`.
    
    See http://ruby-doc.org/core-2.3.1/BasicObject.html#method-i-method_missing
    homu committed Aug 23, 2016
  14. @okkez

    Add missing definition of `respond_to_missing?`

    Because we should overwrite this method when we overwrite
    `method_missing`.
    
    See http://ruby-doc.org/core-2.3.1/BasicObject.html#method-i-method_missing
    okkez committed Aug 23, 2016