| Age | Commit message (Collapse) | Author |
|---|
|
Uses ::RbConfig::CONFIG['host_os']
Found with ruby --disable-gems -e '...'
https://github.com/ruby/resolv/commit/5a5a81ce98
|
|
https://github.com/ruby/optparse/commit/2f9c7500a3
|
|
https://github.com/rubygems/rubygems/commit/e09a6ec815
|
|
https://github.com/rubygems/rubygems/commit/29c085f5f5
|
|
https://github.com/rubygems/rubygems/commit/fa1c51ef59
|
|
rubygems_deprecate_command without rubygems.rb
https://github.com/rubygems/rubygems/commit/4925403686
|
|
at RG 4.1
https://github.com/rubygems/rubygems/commit/e99cdab171
|
|
next major
https://github.com/rubygems/rubygems/commit/15177de84e
|
|
https://github.com/rubygems/rubygems/commit/120c174e7f
|
|
The purpose of this commit is to fix Bug #21188. We need to detect when
stdin has run in to an EOF case. Unfortunately we can't _call_ the eof
function on IO because it will block.
Here is a short script to demonstrate the issue:
```ruby
x = STDIN.gets
puts x
puts x.eof?
```
If you run the script, then type some characters (but _NOT_ a newline),
then hit Ctrl-D twice, it will print the input string. Unfortunately,
calling `eof?` will try to read from STDIN again causing us to need a
3rd Ctrl-D to exit the program.
Before introducing the EOF callback to Prism, the input loop looked
kind of like this:
```ruby
loop do
str = STDIN.gets
process(str)
if str.nil?
p :DONE
end
end
```
Which required 3 Ctrl-D to exit. If we naively changed it to something
like this:
```ruby
loop do
str = STDIN.gets
process(str)
if STDIN.eof?
p :DONE
end
end
```
It would still require 3 Ctrl-D because `eof?` would block. In this
patch, we're wrapping the IO object, checking the buffer for a newline
and length, and then using that to simulate a non-blocking eof? method.
This commit wraps STDIN and emulates a non-blocking `eof` function.
[Bug #21188]
|
|
Paths in environment variables should already be expanded.
The base name of the program is also not subject to expansion.
https://github.com/ruby/optparse/commit/181752391c
|
|
https://github.com/ruby/prism/commit/9f55551b09
|
|
https://github.com/ruby/prism/commit/c2e372a8d8
|
|
|
|
Fixes a TODO now that no reports have been reported in a while.
https://github.com/rubygems/rubygems/commit/f10dc84e7b
|
|
https://github.com/rubygems/rubygems/commit/8078a747b3
|
|
there's no lockfile
The generic Ruby platform was getting unconditionally added in
truffleruby, preventing resolution in situations where there's no
generic ruby version (sorbet-static). Instead, the generic platform
should be considered per dependency, not globally.
https://github.com/rubygems/rubygems/commit/a96afc5351
|
|
Original issue was fixed in JRuby 9.3.0.0, which seems old enough for us
to remove the workaround.
https://github.com/rubygems/rubygems/commit/d285148d39
|
|
After digging into git history a bit, I figure this was about unifying
`bundle cache` and `bundle package`, which already happened a while ago.
So remove this TODO since it's now misleading.
https://github.com/rubygems/rubygems/commit/5a0b06b84d
|
|
This makes it hard to do version checks against this value. The current version checks work because there are so few possible values at the moment.
As an example, PR 3337 introduces new syntax for ruby 3.5 and uses `PM_OPTIONS_VERSION_LATEST` as its version guard. Because what is considered the latest changes every year, it must later be changed to `parser->version == parser->version == PM_OPTIONS_VERSION_CRUBY_3_5 || parser->version == PM_OPTIONS_VERSION_LATEST`, with one extra version each year.
With this change, the PR can instead write `parser->version >= PM_OPTIONS_VERSION_CRUBY_3_5` which is self-explanatory
and works for future versions.
https://github.com/ruby/prism/commit/8318a113ca
|
|
Adds a link to the GitHub Releases page for this gem consistent with other gems in the Ruby organization. Existing examples include:
- [json](https://github.com/ruby/json/blob/master/json.gemspec)
- [ostruct](https://github.com/ruby/ostruct/blob/master/ostruct.gemspec)
https://github.com/ruby/tsort/commit/8086bb33bc
|
|
This gem does not ship any executables.
https://github.com/ruby/shellwords/commit/7da06b91ff
|
|
There are several issues with these which I'm not sure I'll have time to
address properly. I prefer to keep our default branch in a releasable
state just in case. Once they are fixed, this can be reverted.
|
|
https://github.com/ruby/English/commit/6bea25038b
|
|
- The `bundle plugin uninstall --all` was missing.
- The `bundle plugin install --local-git` was missing due to being
deprecated. We decided to reintroduce the doc for more clarity.
https://github.com/rubygems/rubygems/commit/4da252945c
|
|
The changelog line was generating indented more than it should.
https://github.com/rubygems/rubygems/commit/da6109ef5b
|
|
Old versions of BUndler need a workaround to support nested `bundle
exec` invocations by overriding `Gem.activate_bin_path`. However,
RubyGems now uses this new `Gem.activate_and_load_bin_path` helper in
binstubs, which is of course not overridden in those Bundler versions
since it didn't exist at the time.
So, include the override here to workaround that.
https://github.com/rubygems/rubygems/commit/e5ed95e242
|
|
https://github.com/ruby/fileutils/commit/b487f09eed
|
|
https://github.com/ruby/fileutils/commit/c3abf39e7a
|
|
https://github.com/ruby/fileutils/commit/fde0f0713a
|
|
https://github.com/ruby/fileutils/commit/71225b1b46
|
|
https://github.com/ruby/fileutils/commit/f0d7fc817b
|
|
https://github.com/ruby/fileutils/commit/277f7f2ff8
|
|
https://github.com/ruby/fileutils/commit/2836a164ed
|
|
Get rid of failure in rbs.
https://github.com/ruby/fileutils/commit/e44b7b366c
|
|
Several optional positional arguments were incorrectly denoted as
keyword arguments so correct them.
https://github.com/ruby/fileutils/commit/c25f069f96
|
|
In this case, an ArgumentError is now raised rather than ignoring the
option, just as GNU coreutils' `ln` would error on the command line.
Fixes https://github.com/ruby/fileutils/pull/128 as well.
https://github.com/ruby/fileutils/commit/4fc578a75f
|
|
Next version for both will be 4.0.0, however, extra work is necessary to
get CI passing against the new major. So for now, I'm bumping just the
minor version.
|
|
I realized `--redownload` is not a good name, because it does not
necessarily redownloads gems. It only forces reinstallation even if gem
is already installed.
So I believe `--force` is actually a better name and the introduction of
`--force` was a misunderstanding of what the `--force` flag did at the
time.
Let's cancel the deprecation of `--force`.
For now the `--redownload` alias is left around until we decide what to
do with it.
|
|
Rather than crashing when parsing it.
https://github.com/rubygems/rubygems/commit/aa0064e4c7
|
|
deprecation warning
Like others, it's a remembered option which we are deprecating in favor
of configuration.
https://github.com/rubygems/rubygems/commit/801d5dd943
|
|
message
https://github.com/rubygems/rubygems/commit/0af03eea5d
|
|
https://github.com/rubygems/rubygems/commit/d1f8e1c4ac
|
|
https://github.com/rubygems/rubygems/commit/88dd7d2d45
|
|
https://github.com/ruby/erb/commit/e8f3e64581
|
|
[Feature #17473]
|
|
|
|
|
|
https://github.com/ruby/uri/commit/d2a79c6343
|
|
For the references to URI::RFC2396_Parser private methods.
https://github.com/ruby/uri/commit/372fbb455d
|
