[#71439] [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API — matz@...
Issue #11339 has been updated by Yukihiro Matsumoto.
7 messages
2015/11/11
[#71473] Re: [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API
— Eric Wong <normalperson@...>
2015/11/13
Entire series for sockets
[#71450] Ruby 2.3.0-preview1 Released — "NARUSE, Yui" <naruse@...>
Hi,
5 messages
2015/11/11
[#71617] [Ruby trunk - Feature #11664] [PATCH] introduce rb_autoload_value to replace rb_autoload — nobu@...
Issue #11664 has been updated by Nobuyoshi Nakada.
3 messages
2015/11/20
[#71721] [Ruby trunk - Feature #11741] Migrate Ruby to Git from Subversion — me@...
Issue #11741 has been updated by Jon Moss.
4 messages
2015/11/28
[ruby-core:71634] Re: [Ruby trunk - Feature #11731] Make ruby gem install to user-directory by default
From:
Matthew Kerwin <matthew@...>
Date:
2015-11-22 23:12:34 UTC
List:
ruby-core #71634
On 23 November 2015 at 08:56, <kallisti5@unixzen.com> wrote: > Issue #11731 has been updated by Alexander von Gluck. > > > yeah, the large number of workarounds show this is a pretty default > workflow for people. Thus raises the question on why it isn't the default > behavior. > > 窶軌pinion, not fact: is it not the case that most folk who develop independently usually do so where they either a) use rbenv or b) own the machine and can `sudo` safely? And by contrast, the people who can't do that are usually in corporate environments where site-wide installation makes most sense? Note that rbenv isn't just a workaround for this, it also allows independent installation of entire Ruby environments, including core/stdlib, parser, etc. So I don't know that we can say that there's necessarily a large number of workarounds just for local gems. -- Matthew Kerwin http://matthew.kerwin.net.au/