[#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:71630] [Ruby trunk - Feature #11731] [Open] Make ruby gem install to user-directory by default
From:
kallisti5@...
Date:
2015-11-22 20:30:28 UTC
List:
ruby-core #71630
Issue #11731 has been reported by Alexander von Gluck. ---------------------------------------- Feature #11731: Make ruby gem install to user-directory by default https://bugs.ruby-lang.org/issues/11731 * Author: Alexander von Gluck * Status: Open * Priority: Normal * Assignee: ---------------------------------------- Installing gem's system-wide doesn't make sense 99% of the time... * Linux -- Need root access via sudo * Windows -- Need administrator * Max OS X -- Need root access via sudo * Haiku -- /boot/system read-only gem currently installs gems system-wide by default Since the most common use-case is to install gems for your own user, why doesn't gem --user-directory by default? Tools like rvm already set this manually. Making --user-directory default means package maintainers only need to --no-user-directory while everyone else just gem install's -- https://bugs.ruby-lang.org/