Issue #5481 has been updated by hsbt (Hiroshi SHIBATA).


Hi, @headius .

> * Clarify for me please: are the new gemified stdlibs all going to use the default gem mechanism?

I promoted following libraries to default gems at Ruby 2.5

```
cmath csv date dbm digest etc fcntl fiddle fileutils gdbm ipaddr scanf sdbm stringio strscan webrick zlib
```

> * Any "ruby" meta-gem will ideally need an equivalent for JRuby, so it doesn't try to install exts that don't exist for JRuby. It's very important that we don't introduce a bunch of new dependencies to the Ruby world that will be impossible for JRuby to support. We already have issues with folks depending on "openssl" which we do support but which does not have JRuby's pieces in the gem.

I see. But I don't have "ruby" namespace yet. I remember that it needs to support JRuby platform.

> * I will begin trying to get out patches for stdlib libraries into each of the now-gemified libraries.

Please see a repository list: https://github.com/ruby/ruby/commit/9ffa42b995bc1ef9c2b763453f29d42a59755426

I appreciate to merge JRuby code to our default gems. I hope to default gems helps your and JRuby users.


----------------------------------------
Feature #5481: Gemifying Ruby standard library
https://bugs.ruby-lang.org/issues/5481#change-68102

* Author: nahi (Hiroshi Nakamura)
* Status: Assigned
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* Target version: next minor
----------------------------------------
=begin

Up-to-date summary of this proposal is at ((<URL:https://bugs.ruby-lang.org/projects/ruby/wiki/StdlibGem>))

== Motivation

 * ruby's release cycle is slow for some standard libraries;
   * ex. security fix for WEBrick, xmlrpc and Zlib.
   * ex. API iteration for net/http, OpenSSL, json, psych, RDoc, minitest and rake.
 * There's already the feature called 'default gems' in ruby and some stdlibs are already using it:
   * rake, rdoc, minitest, json, io-console, bigdecimal
   * And some gems are already doing out-of-band releases.
 * When releasing we should give independence equally to all stdlibs, but in a consistent and controllable way.

== Proposal

 * Allow out-of-band stdlib releases.
   * We are not proposing changes to ruby's release management, the release manager would decide when they release ruby and stdlib.
 * Allow more stdlibs to be installed as a 'default gem'
 * Register these gems on RubyGems.org
   * Introduce a new mechanism: controlling supported ruby version so that we can avoid installing unexpected version of stdlib gems.
     For example, a WEBrick gem for ruby 2.0.1 (released from ruby_2_0_1 branch) should not be installed for ruby 2.0.0 (released from ruby_2_0_0 branch) unless we know it works for both 2.0.0 and 2.0.1.

Note:

 * Moving stdlibs repository location is not a target of this proposal. The implementation details of stdlib gems should hide this from ruby committers.
 * ruby_1_9_3 is not a target of this proposal. The change should be introduced from 2.0.0 release.


...Some more details of the proposal and discussion topics are going to follow as comments.
=end


---Files--------------------------------
5481.pdf (78.2 KB)


-- 
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>