aboutsummaryrefslogtreecommitdiffstats
path: root/spec/bundler/install/gems/standalone_spec.rb
Commit message (Collapse)AuthorAgeFilesLines
* [rubygems/rubygems] Use modern hashes consistentlyDavid Rodríguez2023-12-071-29/+29
| | | | https://github.com/rubygems/rubygems/commit/bb66253f2c
* [rubygems/rubygems] Drop support for Ruby 2.6 and Ruby 2.7 in BundlerDavid Rodríguez2023-11-131-1/+0
| | | | https://github.com/rubygems/rubygems/commit/93619c97ff
* [rubygems/rubygems] Prevent gem activation in standalone modeDaniel Colson2023-10-031-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | As discussed in https://github.com/rubygems/rubygems/issues/6273#issuecomment-1449176658 The `gem` method behaves awkwardly in standalone mode. Assuming bundler isn't loaded at all, a call to gem might activate a gem that is not part of the bundle (because it's the gem method defined in lib/rubygems/core_ext/kernel_gem.rb and not lib/bundler/rubygems_integration.rb). And when running with `--disable-gems`, the gem method won't be defined at all so we'll get a NoMethodError. Calls to `gem` can appear in dependencies outside an application's control. To work around this at GitHub we defined our own `Kernel#gem` that no-ops. I agree with https://github.com/rubygems/rubygems/issues/6273#issuecomment-1440755882 > people using standalone mode don't want to activate gems like Kernel.gem This commit redefines `Kernel#gem` in the standalone script to no-op. https://github.com/rubygems/rubygems/commit/bea17b55f1
* Merge rubygems/bundler masterHiroshi SHIBATA2023-02-211-1/+30
| | | | Pick from https://github.com/rubygems/rubygems/commit/e9304aed7e43308b99e70c2f7b92028315fee8a5
* Merge RubyGems and Bundler masterHiroshi SHIBATA2023-01-101-1/+1
| | | | from https://github.com/rubygems/rubygems/commit/0635c1423db5d7c461d53bf0c3329bca75de7609
* [rubygems/rubygems] Remove no longer needed `fiddle` hacksDavid Rodríguez2022-09-051-5/+0
| | | | | | | RubyInstaller has released patch versions backporting their changes to not load `fiddle` on boot, so all these are no longer necessary. https://github.com/rubygems/rubygems/commit/05a307deb2
* [rubygems/rubygems] Make `--standalone` play nice with `--local`David Rodríguez2022-07-301-0/+28
| | | | | | | | I'm not sure if using relative paths in the generated script is best for this case, since it makes the script not movable, but that can be improved later. https://github.com/rubygems/rubygems/commit/7f5bdbb842
* [rubygems/rubygems] Fix pending Bundler specsDavid Rodríguez2022-06-261-1/+1
| | | | | | | | | | | | | | | | | | | When testing under the ruby/ruby setup, mkmf.rb needs to the `$extout` global variable set properly. This is because, in this particular case, the `ruby.h` header needed to compile extensions is constructed from `$(extout)/include($arch)/ruby/config.h` but `$extout` is not set by default. I tried to fix this in mkmf.rb itself but I couldn't figure it. But setting it externally to workaround the issue fixes the specs, so I'll start with that. Also setting it externally causes issues when running specs upstream against Ruby 2.3 (I guess because of some difference with Ruby 2.3 mkmf.rb implementation). So I'm avoiding doing it on Ruby 2.3 to woraround that. https://github.com/rubygems/rubygems/commit/d782984585
* [rubygems/rubygems] Fix standalone script generation for statically linked ↵David Rodríguez2022-06-231-5/+23
| | | | | | dev ruby https://github.com/rubygems/rubygems/commit/4d0d7b3c97
* [rubygems/rubygems] Fix extension paths in generated standalone scriptcitrusmoose2022-06-201-1/+2
| | | | | | | | | The paths for extensions of gems would contain the hardcoded ruby version on which the extension was built. This will replace it with runtime ruby version like the parent version directory. It will make the standalone script compatible between different ruby version installations. https://github.com/rubygems/rubygems/commit/a9dae93d5d
* [rubygems/rubygems] Fix generated standalone script for default gemsDavid Rodríguez2022-06-011-1/+8
| | | | | | | | | | | The installer is actually rewriting the spec's full gem path to be the one of the newly installed gem, however the accessor was not properly working for `StubSpecification` instances, and default gems are always of this type, because they are always present locally. Fix the accessor to properly update the underlying full specification. https://github.com/rubygems/rubygems/commit/efa41babfa
* Merge ↵Hiroshi SHIBATA2022-04-281-1/+1
| | | | https://github.com/rubygems/rubygems/commit/3f7d0352e84b29d4a2d4cd93b31e5ebdb5f79cc6
* Merge rubygems master 1e4eda741d732ca1bd7031aef0a16c7348adf7a5Hiroshi SHIBATA2022-04-281-2/+2
|
* Merge RubyGems and Bundler masterHiroshi SHIBATA2022-02-281-1/+2
|
* Sync latest Bundler & RubyGemsDavid Rodríguez2022-02-011-1/+6
|
* Merge RubyGems-3.3.1 and Bundler-2.3.1Hiroshi SHIBATA2021-12-231-1/+1
|
* Merge RubyGems and Bundler masterHiroshi SHIBATA2021-12-151-1/+1
| | | | Merge from https://github.com/rubygems/rubygems/commit/793ad95ecb40e84a1dcb4cb60f2686843ed90de5
* [rubygems/rubygems] Install stringio for standalone spec.Josef Šimánek2021-10-291-1/+1
| | | | | | | | - previously it was required already by net/http, but it is not anymore using ruby-trunk - https://github.com/ruby/net-http/commit/996d18a43f34557cb0b2fcf41b93131d48a235f4 - https://github.com/ruby/ruby/commit/364044e0909692315bd6c2f0e1d968ede9c2beb8#diff-a1d29a94def02829fd4f9ba591199acf079e028f5a2002a77c363eb01212e112 https://github.com/rubygems/rubygems/commit/be1779655a
* [rubygems/rubygems] Fix standalone generated script to deal with path sourcesDavid Rodríguez2021-08-311-0/+30
| | | | | | | | | In the case of path sources, the path the source is pointing to should be added directly to the `$LOAD_PATH` without any modifications. https://github.com/rubygems/rubygems/commit/d3bba936f0 Co-authored-by: Daniel Niknam <mhmd.niknam@gmail.com>
* [rubygems/rubygems] Remove unnecessary `ruby_version` local variableDavid Rodríguez2021-08-311-1/+1
| | | | | | | Under some case, this variable might not end up being used, in which case running the script would print unused variable warnings. https://github.com/rubygems/rubygems/commit/bf96030362
* [rubygems/rubygems] Remove unnecessary `ruby_engine` local variableDavid Rodríguez2021-08-311-1/+1
| | | | | | | Under some case, this variable might not end up being used, in which case running the script would print unused variable warnings. https://github.com/rubygems/rubygems/commit/a2d6392ada
* [rubygems/rubygems] Remove unnecessary `path` local variableDavid Rodríguez2021-08-311-1/+1
| | | | | | We can use `__dir__` directly. https://github.com/rubygems/rubygems/commit/0e6083ca94
* [rubygems/rubygems] Fix standalone install of default gemsDavid Rodríguez2021-08-311-0/+39
| | | | | | Rubygems source replacement was broken. https://github.com/rubygems/rubygems/commit/3549c122f6
* [rubygems/rubygems] Explicitly define a global source for testsDaniel Niknam2021-07-271-0/+1
| | | | | | This is in preparation for deprecating source-less gemfiles. https://github.com/rubygems/rubygems/commit/d6493fa3e2
* Sync latest development version of bundler & rubygemsDavid Rodríguez2021-03-081-0/+39
|
* Track Bundler master(2.3.0.dev) branch at ↵Hiroshi SHIBATA2021-01-041-13/+13
| | | | 55634a8af18a52df86c4275d70fa1179118bcc20
* Merge bundler-2.2.0.rc.2Hiroshi SHIBATA2020-10-151-2/+2
|
* [rubygems/rubygems] Bundler specs - Windows - remove skips, File.open => ↵MSP-Greg2020-07-151-4/+0
| | | | | | | | | | | | | | File.readlines Using File.open without a block leaves a file reference that causes issues with file operations commands/binstubs_spec.rb install/gems/compact_index_spec.rb install/gems/dependency_api_spec.rb install/gems/standalone_spec.rb runtime/executable_spec.rb https://github.com/rubygems/rubygems/commit/4b9a6ca156
* s/sys_exec!/sys_execDavid Rodríguez2020-06-181-2/+2
|
* [rubygems/rubygems] s/bundle!/bundleDavid Rodríguez2020-06-181-10/+10
| | | | https://github.com/rubygems/rubygems/commit/746a4b3d74
* [rubygems/rubygems] Make helpers raise by defaultDavid Rodríguez2020-06-181-1/+1
| | | | https://github.com/rubygems/rubygems/commit/ade0c441d5
* [rubygems/rubygems] Remove `forgotten_command_line_usages` from specsDavid Rodríguez2020-06-051-12/+25
| | | | | | | | Instead, use the non-deprecated option except when specifically testing deprecated CLI flags. In that case, pass the flag directly and limit the specs to `bundler < 3`. https://github.com/rubygems/rubygems/commit/3d5e186241
* [rubygems/rubygems] Reword specs to not mention deprecated flagsDavid Rodríguez2020-06-051-3/+3
| | | | https://github.com/rubygems/rubygems/commit/f878a81f22
* Marked the failing examples with the current master branch on ruby repositoryHiroshi SHIBATA2020-05-221-1/+1
|
* Sync Bundler PR #3624Hiroshi SHIBATA2020-05-221-7/+7
|
* Update the bundler version with master branchHiroshi SHIBATA2020-05-131-84/+60
|
* [bundler/bundler] Normalize file:// handling in specsDavid Rodríguez2019-08-031-5/+5
| | | | https://github.com/bundler/bundler/commit/5946d62ad0
* Merge bundler master from upstream.Hiroshi SHIBATA2019-06-091-8/+8
| | | | Pick from 8dd59e3ba97eb80a599f8149f31bf40773b69dc0
* Merge Bundler 2.1.0.pre.1 as developed version from upstream.hsbt2019-04-141-3/+3
| | | | | | https://github.com/bundler/bundler/commit/a53709556b95a914e874b22ed2116a46b0528852 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67539 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Merge Bundler 2.0.1 from upstream.hsbt2019-01-041-3/+3
| | | | git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66710 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Downgrade Bundler 1.17.x from 2.0.0.hsbt2018-12-111-3/+3
| | | | | | | | We have the platform issue on heroku: * https://gist.github.com/schneems/26452540f6e2bbbcf2ea144f45f6b305 * https://github.com/heroku/heroku-buildpack-ruby/issues/833 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66323 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Merge upstream changes from 2-0-stable branch of bundler/bundler.hsbt2018-11-041-3/+3
| | | | | | * It update bundler 2 mode to bundler 3. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65523 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Added bundler as default gems. Revisit [Feature #12733]hsbt2018-11-021-0/+337
| | | | | | | | | | | * bin/*, lib/bundler/*, lib/bundler.rb, spec/bundler, man/*: Merge from latest stable branch of bundler/bundler repository and added workaround patches. I will backport them into upstream. * common.mk, defs/gmake.mk: Added `test-bundler` task for test suite of bundler. * tool/sync_default_gems.rb: Added sync task for bundler. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65509 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Postponing the Bundler merge.hsbt2017-12-221-321/+0
| | | | | | | I faced a big issue about Bundler with ruby core. I have no time to resolve it issue before 2.5 final release. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@61416 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Update bundled bundler to 1.16.0.hsbt2017-11-011-21/+24
| | | | | | | * lib/bundler, spec/bundler: Merge bundler-1.16.0. * common.mk: rspec examples of bundler-1.16.0 needs require option. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@60603 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
* Merge bundler to standard libraries.hsbt2017-09-081-0/+318
rubygems 2.7.x depends bundler-1.15.x. This is preparation for rubygems and bundler migration. * lib/bundler.rb, lib/bundler/*: files of bundler-1.15.4 * spec/bundler/*: rspec examples of bundler-1.15.4. I applied patches. * https://github.com/bundler/bundler/pull/6007 * Exclude not working examples on ruby repository. * Fake ruby interpriter instead of installed ruby. * Makefile.in: Added test task named `test-bundler`. This task is only working macOS/linux yet. I'm going to support Windows environment later. * tool/sync_default_gems.rb: Added sync task for bundler. [Feature #12733][ruby-core:77172] git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@59779 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-24 14:29:36 +0000