ruby.git/lib/bundler/installer/standalone.rb, branch v3_4_9

[rubygems/rubygems] More aggressive `Performance/FlatMap` cop configuration

2024-11-26T06:11:05+00:00

https://github.com/rubygems/rubygems/commit/d8d68cc00e

[rubygems/rubygems] Fix gemspec `require_paths` type validation

2024-07-18T09:25:17+00:00

It was not properly being detected as an Array attribute, and thus not
properly validated.

Fixing this allows us to remove a strange `rescue` clause in Bundler.

https://github.com/rubygems/rubygems/commit/4121a32408

[rubygems/rubygems] Use modern hashes consistently

2023-12-07T22:29:33+00:00

https://github.com/rubygems/rubygems/commit/bb66253f2c

[rubygems/rubygems] Prevent gem activation in standalone mode

2023-10-03T17:16:19+00:00

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

[rubygems/rubygems] Centralize logic using `Pathname#relative_path_from`

2023-09-27T05:20:58+00:00

To avoid potential crashes when trying to jump from a drive to another
on Windows, and take the change refactor things a bit.

https://github.com/rubygems/rubygems/commit/7c9a9a431a

[rubygems/rubygems] Allow standalone mode to work on a Windows edge case

2023-09-25T07:13:21+00:00

If a gem is located in a different drive than the Gemfile, standalone
mode will fail to generate the `bundler/setup` script, failing with an
error like

```
ArgumentError: different prefix: "C:/" and "D:/a/rubygems/rubygems/bundler/tmp/2/bundled_app/bundle/bundler"
  C:/hostedtoolcache/windows/Ruby/3.0.5/x64/lib/ruby/3.0.0/pathname.rb:528:in `relative_path_from'
  D:/a/rubygems/rubygems/bundler/tmp/2/gems/system/gems/bundler-2.4.20/lib/bundler/installer/standalone.rb:58:in `gem_path'
  D:/a/rubygems/rubygems/bundler/tmp/2/gems/system/gems/bundler-2.4.20/lib/bundler/installer/standalone.rb:33:in `block (2 levels) in paths'
  D:/a/rubygems/rubygems/bundler/tmp/2/gems/system/gems/bundler-2.4.20/lib/bundler/installer/standalone.rb:32:in `map'
  D:/a/rubygems/rubygems/bundler/tmp/2/gems/system/gems/bundler-2.4.20/lib/bundler/installer/standalone.rb:32:in `block in paths'
```

I'm fixing this by falling back to using a full path in this case.

This was caught by a failing spec, so I'm not adding new specs.

https://github.com/rubygems/rubygems/commit/3cb9b9ab7a

[rubygems/rubygems] Use Kernel.singleton_class

2023-08-01T00:31:22+00:00

https://github.com/rubygems/rubygems/commit/9be984f281

Merge rubygems/bundler master

2023-02-21T10:28:12+00:00

  Pick from https://github.com/rubygems/rubygems/commit/e9304aed7e43308b99e70c2f7b92028315fee8a5

[rubygems/rubygems] Make `--standalone` play nice with `--local`

2022-07-29T19:24:25+00:00

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 standalone script generation for statically linked dev ruby

2022-06-23T09:17:37+00:00

https://github.com/rubygems/rubygems/commit/4d0d7b3c97