| Age | Commit message (Collapse) | Author |
|
https://github.com/rubygems/rubygems/commit/b1d825ab3a
|
|
Fixes #2290.
1. `Gem::Specification.date` returns SOURCE_DATE_EPOCH when defined,
2. this commit makes RubyGems set it _persistently_ when not provided.
This combination means that you can build a gem, check the build time,
and use that value to generate a new build -- and then verify they're
the same.
https://github.com/rubygems/rubygems/commit/d830d53f59
|
|
https://github.com/rubygems/rubygems/commit/5b81f364ae
|
|
Cfuncs that use rb_scan_args with the : entry suffer similar keyword
argument separation issues that Ruby methods suffer if the cfuncs
accept optional or variable arguments.
This makes the following changes to : handling.
* Treats as **kw, prompting keyword argument separation warnings
if called with a positional hash.
* Do not look for an option hash if empty keywords are provided.
For backwards compatibility, treat an empty keyword splat as a empty
mandatory positional hash argument, but emit a a warning, as this
behavior will be removed in Ruby 3. The argument number check
needs to be moved lower so it can correctly handle an empty
positional argument being added.
* If the last argument is nil and it is necessary to treat it as an option
hash in order to make sure all arguments are processed, continue to
treat the last argument as the option hash. Emit a warning in this case,
as this behavior will be removed in Ruby 3.
* If splitting the keyword hash into two hashes, issue a warning, as we
will not be splitting hashes in Ruby 3.
* If the keyword argument is required to fill a mandatory positional
argument, continue to do so, but emit a warning as this behavior will
be going away in Ruby 3.
* If keyword arguments are provided and the last argument is not a hash,
that indicates something wrong. This can happen if a cfunc is calling
rb_scan_args multiple times, and providing arguments that were not
passed to it from Ruby. Callers need to switch to the new
rb_scan_args_kw function, which allows passing of whether keywords
were provided.
This commit fixes all warnings caused by the changes above.
It switches some function calls to *_kw versions with appropriate
kw_splat flags. If delegating arguments, RB_PASS_CALLED_KEYWORDS
is used. If creating new arguments, RB_PASS_KEYWORDS is used if
the last argument is a hash to be treated as keywords.
In open_key_args in io.c, use rb_scan_args_kw.
In this case, the arguments provided come from another C
function, not Ruby. The last argument may or may not be a hash,
so we can't set keyword argument mode. However, if it is a
hash, we don't want to warn when treating it as keywords.
In Ruby files, make sure to appropriately use keyword splats
or literal keywords when calling Cfuncs that now issue keyword
argument separation warnings through rb_scan_args. Also, make
sure not to pass nil in place of an option hash.
Work around Kernel#warn warnings due to problems in the Rubygems
override of the method. There is an open pull request to fix
these issues in Rubygems, but part of the Rubygems tests for
their override fail on ruby-head due to rb_scan_args not
recognizing empty keyword splats, which this commit fixes.
Implementation wise, adding rb_scan_args_kw is kind of a pain,
because rb_scan_args takes a variable number of arguments.
In order to not duplicate all the code, the function internals need
to be split into two functions taking a va_list, and to avoid passing
in a ton of arguments, a single struct argument is used to handle
the variables previously local to the function.
Notes:
Merged-By: jeremyevans <code@jeremyevans.net>
|
|
https://github.com/rubygems/rubygems/commit/d4fc383497
|
|
https://github.com/rubygems/rubygems/commit/95c1f4e179
|
|
https://github.com/rubygems/rubygems/commit/f5972338e0
|
|
https://github.com/rubygems/rubygems/commit/d1bb122651
|
|
is specified
https://github.com/rubygems/rubygems/commit/547947bbf0
|
|
https://github.com/rubygems/rubygems/commit/ab186266b7
|
|
https://github.com/rubygems/rubygems/commit/dc70c5a192
|
|
https://github.com/rubygems/rubygems/commit/4ba4ffebbe
|
|
https://github.com/rubygems/rubygems/commit/a16eacd650
|
|
Instead, display an informative message saying that uninstallation of
specific versions is being skipped because of being default gems.
https://github.com/rubygems/rubygems/commit/b44845aa1d
|
|
instance
https://github.com/rubygems/rubygems/commit/9a401646e1
|
|
https://github.com/rubygems/rubygems/commit/fc224e9717
|
|
Mostly requires adding ** in either calls or method definitions.
Notes:
Merged: https://github.com/ruby/ruby/pull/2395
|
|
`Kernel#pp` has wrapper, but `PP` does not.
https://github.com/ruby/ruby/runs/207405029#step:10:141
`NameError: uninitialized constant Bundler::Molinillo::Resolver::Resolution::PP`
|
|
It is defined since ruby 1.9.2.
https://github.com/rubygems/rubygems/commit/84981ca908
|
|
Installed path may contain symbolic links.
|
|
|
|
This reverts commit 260ef51a73c067599826c8ab110c53994c1b6226.
This broke the stable versions of Ruby like 2.4 and 2.5
|
|
|
|
|
|
|
|
|
|
This reverts commit 75d29db8f965893bb6ab38b9008abc80cdda246e.
|
|
This reverts commit 00cd5d74cecb6aa4a184e57e2b8246ef6e45d458.
|
|
Caused by 00cd5d74ce
|
|
https://github.com/rubygems/rubygems/commit/5924286ae2
|
|
use ruby_exe in heredocs instead of ruby.exe
https://github.com/rubygems/rubygems/commit/9f1b7d6590
|
|
https://github.com/rubygems/rubygems/commit/c0275ee537
|
|
https://github.com/rubygems/rubygems/commit/1133c2f700
|
|
https://github.com/rubygems/rubygems/commit/8702f59d32
|
|
https://github.com/rubygems/rubygems/commit/bb02953a97
|
|
I think this should be more efficient?
https://github.com/rubygems/rubygems/commit/a1de78104f
|
|
Gem::Command#show_lookup_failure with a parameter to suppress suggestions
https://github.com/rubygems/rubygems/commit/760b7d834f
|
|
https://github.com/rubygems/rubygems/commit/fc3f722164
|
|
https://github.com/rubygems/rubygems/commit/41e60cdb6b
|
|
https://github.com/rubygems/rubygems/commit/6fbda98eb3
|
|
|
|
Now Proc#to_s returns
"#<Proc:0x00000237a0f5f170@t.rb:1>".
However, it is convenient to select a file name by (double-)clicking
on some terminals by separating ' ' instead of '@' like
"#<Proc:0x00000237a0f5f170 t.rb:1>"
[Feature #16101]
|
|
|
|
JRUBY_VERSION
* RUBY_ENGINE and RUBY_ENGINE_VERSION are defined on every modern Ruby.
* There is no such constant as TRUFFLERUBY_VERSION or RBX_VERSION.
https://github.com/rubygems/rubygems/commit/431d0aefdd
|
|
https://github.com/rubygems/rubygems/commit/83eced0b39
|
|
https://github.com/rubygems/rubygems/commit/5c3158d975
|
|
https://github.com/rubygems/rubygems/commit/b0588a87b1
|
|
* `Gem::ConfigMap` is still used by Bundler.
* `Gem::RubyGemsVersion` is also still referred by the old gems.
https://github.com/rubygems/rubygems/commit/249c3ff44f
|
|
set it up later and cause confusion
https://github.com/rubygems/rubygems/commit/6ec3ba983c
|
|
not needed anymore
https://github.com/rubygems/rubygems/commit/930de86a24
|