| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| | |
Version 1.13.0.rc.1
|
| | |
|
| |
| |
| |
| |
| |
| | |
Fix hardcoded bundler version string in trampoline specs
(cherry picked from commit 7332185811d77a51cc228d7e18ccbe4f5e553f3a)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
[LockfileParser] Support for old RG on Ruby 2.3+
Fixes #4698
\c @allenzhao
(cherry picked from commit 78d614413a994b5acd3dccd82b0782290d0d850d)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Unset GEM_PATH with nil not empty string.
This should fix #4592, the tests all pass, but the line of code in
question goes back to 2010, so this sorta seems slightly dangerous, but
it's probable the circumstances of hitting this line in conjunction with
`bundle exec` is a combination that didn't exist prior to 1.12.x.
Issue #4592 has a full diagnosis, but the gist of it is this: if an
empty string is passed as the `GEM_PATH` to the subsequent process
launched by `bundle exec`, then if the `cmd` portion of `bundle exec` is
a ruby shebanged file, then if the current bundle install uses a local
path (`disable_shared_gems` is true) then it won't be able to find the
bundler gem at all because Bundler doesn't install itself into its own
Bundle, it's only installed in the system gems for the Ruby.
`nil` must be passed because the RubyGems code that sets up the
`GEM_PATH` does a conditional on the current `GEM_PATH` and empty string
evaluates to true, whereas `nil` evaluates to false. In the false case
the `GEM_PATH` is internally populated with the system gems path such
that the bundler gem can be found.
(cherry picked from commit 37064b3a900475e684dd090d332b88d4c888c128)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add machinery for printing major deprecations
First step towards handling all of #4695
\c @RochesterinNYC @indirect
(cherry picked from commit dca6d26833ddd9d9de658bef7274c8fa21014c44)
|
| |
| |
| |
| |
| |
| |
| |
| | |
[Definition] Add a #change_reason printed in debug
@indirect this might make your debugging a bit easier?
(cherry picked from commit 378602f073f808046741a829903d6ea6104f619a)
|
| |
| |
| |
| |
| |
| |
| |
| | |
Prefer spec name matches when searching for an exe
Closes #4705.
(cherry picked from commit d497e04e336fcb54f6f92acbb6665b84d11ca396)
|
| |
| |
| |
| |
| |
| | |
[Trampoline] Dont change the load path just for postit
(cherry picked from commit bacb0e7835996df44681f84bf662dbe0fb9deb30)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Don't incorrectly relativize sibling `--path` with the same prefix
Given current working directory `/foo/app`, when you install with
`--path /foo/app_cache`, ensure that the messaging says:
Bundled gems are installed into /foo/app_cache
instead of the incorrect:
Bundled gems are installed into ._cache
(cherry picked from commit 3b928d83c1b606b4598c6662528b20482762a14d)
|
| |
| |
| |
| |
| |
| |
| |
| | |
[Definition] Just search for changed specs in an exactly matching source
\c @indirect
(cherry picked from commit faf82ccc97ab2441bd4fe849d12151fb347a81cf)
|
| |
| |
| |
| |
| |
| |
| |
| | |
disable trampoline in dbundle
/cc @segiddins
(cherry picked from commit b44d763965d3551a734a57fd828d13f9908d0bad)
|
| |
| |
| |
| |
| |
| | |
[GitProxy] Deinit submodules if they are not requested
(cherry picked from commit 5e88c8d494d40157dd1ec9b34be8aafe68431a90)
|
|\ \
| | |
| | |
| | | |
[GitProxy] Deinit submodules if they are not requested
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
disable trampoline in dbundle
/cc @segiddins
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
[Definition] Just search for changed specs in an exactly matching source
\c @indirect
|
| | | | | |
|
| | |/ /
| |/| | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Don't incorrectly relativize sibling `--path` with the same prefix
Given current working directory `/foo/app`, when you install with
`--path /foo/app_cache`, ensure that the messaging says:
Bundled gems are installed into /foo/app_cache
instead of the incorrect:
Bundled gems are installed into ._cache
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Given current working directory `/foo/app`, when you install with
`--path /foo/app_cache`, ensure that the messaging says:
Bundled gems are installed into /foo/app_cache
instead of the incorrect:
Bundled gems are installed into ._cache
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
[Trampoline] Dont change the load path just for postit
|
| | |/ /
| |/| | |
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | | |
Prefer spec name matches when searching for an exe
Closes #4705.
|
| |/ / |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | | |
[Definition] Add a #change_reason printed in debug
@indirect this might make your debugging a bit easier?
|
| | | |
|
|/ /
| |
| |
| | |
This could cause definition to think bundler is being updated
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add machinery for printing major deprecations
First step towards handling all of #4695
\c @RochesterinNYC @indirect
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ /
| |
| |
| | |
Will make future diffs much easier to read
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Unset GEM_PATH with nil not empty string.
This should fix #4592, the tests all pass, but the line of code in
question goes back to 2010, so this sorta seems slightly dangerous, but
it's probable the circumstances of hitting this line in conjunction with
`bundle exec` is a combination that didn't exist prior to 1.12.x.
Issue #4592 has a full diagnosis, but the gist of it is this: if an
empty string is passed as the `GEM_PATH` to the subsequent process
launched by `bundle exec`, then if the `cmd` portion of `bundle exec` is
a ruby shebanged file, then if the current bundle install uses a local
path (`disable_shared_gems` is true) then it won't be able to find the
bundler gem at all because Bundler doesn't install itself into its own
Bundle, it's only installed in the system gems for the Ruby.
`nil` must be passed because the RubyGems code that sets up the
`GEM_PATH` does a conditional on the current `GEM_PATH` and empty string
evaluates to true, whereas `nil` evaluates to false. In the false case
the `GEM_PATH` is internally populated with the system gems path such
that the bundler gem can be found.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This should fix #4592, the tests all pass, but the line of code in
question goes back to 2010, so this sorta seems slightly dangerous, but
it's probable the circumstances of hitting this line in conjunction with
`bundle exec` is a combination that didn't exist prior to 1.12.x.
Issue #4592 has a full diagnosis, but the gist of it is this: if an
empty string is passed as the `GEM_PATH` to the subsequent process
launched by `bundle exec`, then if the `cmd` portion of `bundle exec` is
a ruby shebanged file, then if the current bundle install uses a local
path (`disable_shared_gems` is true) then it won't be able to find the
bundler gem at all because Bundler doesn't install itself into its own
Bundle, it's only installed in the system gems for the Ruby.
`nil` must be passed because the RubyGems code that sets up the
`GEM_PATH` does a conditional on the current `GEM_PATH` and empty string
evaluates to true, whereas `nil` evaluates to false. In the false case
the `GEM_PATH` is internally populated with the system gems path such
that the bundler gem can be found.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[LockfileParser] Support for old RG on Ruby 2.3+
Fixes #4698
\c @allenzhao
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | | |
Change Rakefile to work as a RubyGems submodule
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | | |
Fix hardcoded bundler version string in trampoline specs
|
|/ / / |
|