| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/12444
|
|
has been changed
Use Process.argv0 instead of $PROGRAM_NAME because $PROGRAM_NAME is
liable to be changed but Process.argv0 is not.
https://github.com/rubygems/rubygems/commit/43b747dc9e
|
|
https://github.com/rubygems/rubygems/commit/23d06195fa
|
|
the overwritten binstub in the test has a final new line that makes it
not match "OMG" exactly from the beginning, that's why the test passes,
but `bintubs` command without `--force` flag is not supposed to update
the binstub.
This change fixes the test to test what's supposed to update the
binstub, and also fixes the assertion that that it will fail in the
future if `--force` stops updating the binstub.
https://github.com/rubygems/rubygems/commit/dfc9023337
|
|
|
|
https://github.com/rubygems/rubygems/commit/f530f8686d
|
|
https://github.com/rubygems/rubygems/commit/9548aa6766
|
|
https://github.com/rubygems/rubygems/commit/ce9f6285c4
|
|
for some reason
https://github.com/rubygems/rubygems/commit/f8f589b1b8
|
|
Signed-off-by: Samuel Giddins <segiddins@segiddins.me>
https://github.com/rubygems/rubygems/commit/06eec6d855
|
|
|
|
https://github.com/rubygems/rubygems/commit/72d8d4dbba
|
|
https://github.com/rubygems/rubygems/commit/47b7e50f64
|
|
This was introduced by https://github.com/rubygems/rubygems/commit/0b7be7bb7705, because
the original patch was not adapted to some recent refactorings.
https://github.com/rubygems/rubygems/commit/0bca60d6e5
Co-authored-by: Hiroshi SHIBATA <hsbt@ruby-lang.org>
|
|
available remotely
https://github.com/rubygems/rubygems/commit/1a7a3fdeb9
|
|
https://github.com/rubygems/rubygems/commit/907d46964d
|
|
A spec needed changes because now loading the default `json` prints a
warning about `ostruct` getting loaded although it will be removed in
the future. Use a different default gem to test this.
https://github.com/rubygems/rubygems/commit/7415a66906
Co-authored-by: Samuel Giddins <segiddins@segiddins.me>
|
|
has extensions and `gemspec` DSL is being used
In a `bundle exec` context, the local specification will actually be
part of the known specifications, so RubyGems will assume it has already
been installed, which is not actually true.
This will cause `RequestSet` to rebuild extensions for a gem that's not
actually installed, causing errors.
The fix is to make sure detection of installed activation requests
considers not only that there's a known spec with the same full name as
the one being installed, but also that this spec is installed in the
same gem_home were pretend to install the new gem.
https://github.com/rubygems/rubygems/commit/a8ef1286a6
|
|
`make test-bundler` on ruby/ruby don't have installed gemspec.
So, `require "psych"` didn't activate psych as default gems on ruby repo.
https://github.com/rubygems/rubygems/commit/f8ca514cbb
|
|
https://github.com/rubygems/rubygems/commit/6b1e8a14bd
|
|
https://github.com/rubygems/rubygems/commit/0658903e25
|
|
While working on something else I noticed:
* Usage of uppercased "RUBY" and "JAVA" as platforms, when those don't
really exist.
* Usage of some test gems with "1.0" as gemspec version and "1.0.0" as
actual version.
This commit fixes both inconsistencies to make things more expectable.
https://github.com/rubygems/rubygems/commit/e3ec32e247
|
|
https://github.com/rubygems/rubygems/commit/6d6646b8bc
|
|
add_runtime_dependency
https://github.com/rubygems/rubygems/commit/9a08043858
|
|
|
|
binstubs
https://github.com/rubygems/rubygems/commit/076aba8b1c
|
|
Pathname problem
Recent refactorings in test suite to not load `pathname` for launching
Bundler subprocesses make some specs fail due to the warnings Ruby prints
when autoloading `pathname` under a namespace. But enabling this spec
also reproduces the hard error it produces on truffleruby.
https://github.com/rubygems/rubygems/commit/e47cd78081
|
|
https://github.com/rubygems/rubygems/commit/2d9eeadb62
|
|
any other gem
For backwards compatibility, make sure default gems are still used as a
last resort when materializing, in case no remote, cached, or installed
specs are found.
https://github.com/rubygems/rubygems/commit/93788f689f
|
|
cache
Even if all gems are properly installed and no resolve is needed, we
recently started always reading all packages in `vendor/cache` and
extracting specifications from them.
This commit fixes the problem by longer making considering cached specs
the default and only enable them when a resolve is actually needed.
https://github.com/rubygems/rubygems/commit/edeb2c42bf
|
|
https://github.com/rubygems/rubygems/commit/241d0aafcd
|
|
We have some places that already use `bundle config auto_install true`,
ie:
https://github.com/technicalpickles/rubygems/blob/7a144f3374f6a400cc9832f072dc1fc0bca8c724/bundler/lib/bundler/cli.rb#L11
This applies the same logic (copy and pasted) to happen when you
`require "bundler/setup"`.
https://github.com/rubygems/rubygems/commit/bb3c922341
|
|
I apparently did that to fix some issue with case insensitivity but I
didn't add a spec, and I think not upcasing should not cause issues.
https://github.com/rubygems/rubygems/commit/1b6f23275a
|
|
https://github.com/rubygems/rubygems/commit/f79a6a004d
|
|
|
|
https://github.com/rubygems/rubygems/commit/3a262f55c8
|
|
https://github.com/rubygems/rubygems/commit/7f35dc19c5
|
|
A default Bundler copy with vendored net-http is causing a Bundler spec
to end up loading that copy instead of the copy of Bundler under test.
This is because of vcr, but we don't really need vcr in the command
that's failing, so I avoided loading it.
https://github.com/rubygems/rubygems/commit/304ab6e1b9
|
|
This reverts commit https://github.com/rubygems/rubygems/commit/091b4fcf2b99.
https://github.com/rubygems/rubygems/commit/dcade3235f
|
|
If a gem is specified in the Gemfile (or resolved as a transitive
dependency), it's always resolved from remote/installed sources. Default
gems are only used as a fallback for gems not included in the bundle.
I believe this leads to more consistent behavior and more portable apps,
since all gems will be installed to the configured bundle path,
regardless of whether they are default gems or not.
https://github.com/rubygems/rubygems/commit/091b4fcf2b
|
|
https://github.com/rubygems/rubygems/commit/2662e45d75
|
|
https://github.com/rubygems/rubygems/commit/bdb78d8289
|
|
https://github.com/rubygems/rubygems/commit/ef97ad37bd
|
|
|
|
And make it easier to update next time.
https://github.com/rubygems/rubygems/commit/1ea4bfa5d8
|
|
https://github.com/rubygems/rubygems/commit/bb66253f2c
|