| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
- Closes #4317
|
| |
|
| |
|
|\
| |
| |
| |
| |
| | |
[CLI] Ensure `bundle install` will always install
Closes #3966.
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
[Exec] Load instead of exec-ing
Proof-of-concept to avoid `exec` where possible, instead just using `load` when we'd be launching the same interpreter anyways. About a .2 second gain in my limited testing. Over a second gain in jruby in my testing, somehow.
Not near ready for merging, but pretty cool for an hour of hacking.
- [x] Tests
- [ ] Centralize error handling
- [ ] Raise exceptions instead of exiting
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
Skip building git gem extensions if they're already built
None
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
extensions dir
|
| | | | |
|
| | | |
| | | |
| | | | |
closes #4082
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
this guarantees that even if rubygems somehow memoizes a value from the
original method, we will use our own value instead.
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
RochesterinNYC:improved-error-message-when-different-platform, r=segiddins
Add platform info to error message for different platform in gemspec than Gemfile.lock
- Addresses #4259
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Gemfile.lock
- Closes #4259
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
r=indirect
Add `--frozen` flag support for `bundle package`
- Closes #3356
|
| |/ /
| | |
| | |
| | | |
- Closes #3356
|
|/ /
| |
| |
| |
| | |
- `bundle outdated --patch` will only report updates in the patch
version (v#.#.patch)
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
[Resolver] Update Molinillo to 0.4.3
See https://github.com/CocoaPods/Molinillo/releases/0.4.3.
Closes https://github.com/bundler/bundler/issues/4276.
|
| |/ |
|
|/
|
|
|
|
| |
- `bundle outdated --minor` should only report updates in the minor
version (not "at least minor version")
- Create shared example unit spec for ignoring major version updates
|
|
|
|
| |
- Closes #4288
|
| |
|
|
|
|
|
| |
- (frozen state ex. after `bundle install --deployment`)
- closes #4287
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
RochesterinNYC:add-clarifying-usage-message-for-deployment-and-system, r=indirect
Add alternative error message for when `--deployment` and `--system` flags are both used on `bundle install`
Calling `bundle install --deployment --system` currently results in the following error message:
```
$ bundle install --deployment --system
You have specified both a path to install your gems to,
as well as --system. Please choose.
```
which is a little confusing.
This PR changes the behavior to:
```
$ bundle install --deployment --system
You have specified both --deployment as well as --system. Please choose. #<-- in red
```
|
| |
| |
| |
| | |
flags are both used on `bundle install`
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
RochesterinNYC:add-error-message-for-shared-helpers-EPROTO, r=indirect
Raise new `Bundler::VirtualProtocolError` in response to `Errno::EPROTO`
- Related to #4163, #3932, and #3581
Ideally, a custom error and/or error message would be returned in these cases rather than just error out because of the uncaught `Errno::EPROTO`.
I'd like some feedback on what the appropriate error message should be however. The caveat is that it seems like a wide range of errors (possibly any error?) that occur in the presence of virtualization will raise this `Errno::EPROTO` error.
|
| |/
| |
| |
| |
| |
| |
| |
| | |
`Bundler::SharedHelpers#filesystem_access`
will raise in response to Errno::EPROTO
- Provides better error message/handling for #4163
|
|\ \
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
Place bundler loaded gems after -I and RUBYLIB
Previously, gems were being placed at the front of the LOAD_PATH. This
meant you couldn't override a gem by setting -I or RUBYLIB.
This patch places -I and RUBYLIB in front of loaded gems and matches the
behavior in RubyGems.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, gems were being placed at the front of the LOAD_PATH. This
meant you couldn't override a gem by setting -I or RUBYLIB.
This patch places -I and RUBYLIB in front of loaded gems and matches the
behavior in RubyGems.
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
RochesterinNYC:add-porcelain-parseable-flag-bundle-outdated, r=indirect
Add --parseable (with --porcelain alias) to `bundle outdated` for minimal output
- This flag changes the output of bundle outdated from:
```
* activesupport (newest 3.0, installed 2.3.5, requested = 2.3.5) in groups "development, test"
```
to
```
activesupport (newest 3.0, installed 2.3.5, requested = 2.3.5)"
```
and removes the extraneous output relating to fetching gem metadata,
version metadata, git updates, and resolving dependencies.
- Addresses bundler/bundler-features#85
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- This flag changes the output of bundle outdated from:
```
* activesupport (newest 3.0, installed 2.3.5, requested = 2.3.5) in groups "development, test"
```
to
```
activesupport (newest 3.0, installed 2.3.5, requested = 2.3.5)"
```
and removes the extraneous output relating to fetching gem metadata,
version metadata, git updates, and resolving dependencies.
- Addresses bundler/bundler-features#85
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
RochesterinNYC/improve-error-message-invalid-gemspec-for-dependency
Add helpful invalid gemspec error message for `bundle install --standalone`
|
| | | |
| | | |
| | | |
| | | | |
--standalone` when a gem/dependency has an invalid gemspec
|
|/ / / |
|
|/ /
| |
| |
| |
| | |
The comment feels a bit misleading. It sounds like this allows Rubygems
pushes by default which it does not
|