| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | |
|
|/ / / / |
|
|\ \ \ \
| |/ / /
|/| | |
| | | | |
[Env] Support running `bundle env` when not inside a bundle
|
|/ / / |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | | |
[Exec] Add specs for $0 and __FILE__ when loaded
Tests for #4488
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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).
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
# Conflicts:
# lib/bundler/cli/doctor.rb
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
:specific_platform is enabled
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Most of the developers should already properly configured "git config
user.name". This save time and avoid generated README.md with wrong
GitHub url.
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Add OpenSSL::OPENSSL_VERSION to `bundle env`
|
| | | | | |
|
|\ \ \ \ \
| |_|_|/ /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
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` stands to signify
whether the generated stubs will require the Bundler runtime or not.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[Resolver] Ensure all platforms are activated for the activated spec group
Closes #4896
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |/ / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
[RubyGemsGemInstaller] Validate checksums from the compact index
Closes #4464
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|