[#84280] [Ruby trunk Bug#14181] hangs or deadlocks from waitpid, threads, and trapping SIGCHLD — nobu@...
Issue #14181 has been updated by nobu (Nobuyoshi Nakada).
3 messages
2017/12/15
[#84398] [Ruby trunk Bug#14220] WEBrick changes - failures on MSWIN, MinGW — Greg.mpls@...
Issue #14220 has been reported by MSP-Greg (Greg L).
3 messages
2017/12/22
[#84472] Re: [ruby-dev:50394] [Ruby trunk Bug#14240] warn four special variables: $; $, $/ $\ — Eric Wong <normalperson@...>
Shouldn't English posts be on ruby-core instead of ruby-dev?
3 messages
2017/12/26
[ruby-core:84221] [Ruby trunk Bug#5060] Executables in bin folder conflict with their gem versions.
From:
v.ondruch@...
Date:
2017-12-12 14:54:44 UTC
List:
ruby-core #84221
Issue #5060 has been updated by vo.x (Vit Ondruch). No, this is still not resolved (testing with r61169). Only Rake (which is "bundled" gem) appears to be have RubyGems generated stub which won't conflict unless RubyGems changes the algorithm. The remaining executables (namely bundle, bundler, rdoc) are conflicting. ---------------------------------------- Bug #5060: Executables in bin folder conflict with their gem versions. https://bugs.ruby-lang.org/issues/5060#change-68343 * Author: vo.x (Vit Ondruch) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * Target version: next minor * ruby -v: 1.9.3 * Backport: ---------------------------------------- It would be nice if the executables for rdoc, rake, ri, etc. locate in bin folder, would be standard RubyGems stubs. Otherwise, once there is installed version of such library as a gem, the original file is rewritten and the functionality of bundled library is lost. But my main concern is the conflict between ruby and gem executables, since it makes packaging for Linux distributions hard (for Fedora and RHEL in my case). -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>