* To test, install Ruby 1.9.3 and the rebuilt packages from the testing repository http://vondruch.fedorapeople.org/ruby_1.9.3.repo . For more updates, please follow the Ruby-SIG mailing list thread http://lists.fedoraproject.org/pipermail/ruby-sig/2011-December/000705.html . We hope to have available dedicated BuildRoot in Koji, soon.

+

* To test, install Ruby 1.9.3 and the rebuilt packages from the testing repository http://vondruch.fedorapeople.org/ruby_1.9.3.repo . Or better, ẗhere is already available f17-ruby tag in Koji, so you can use Koji repository http://kojipkgs.fedoraproject.org/repos/f17-ruby/latest/$basearch for testing. For more updates, please follow the Ruby-SIG mailing list thread http://lists.fedoraproject.org/pipermail/ruby-sig/2011-December/000705.html .

* Use the packages, ideally with your applications previously written in Ruby (be sure to upgrade your applications to Ruby 1.9.3 first).

* Use the packages, ideally with your applications previously written in Ruby (be sure to upgrade your applications to Ruby 1.9.3 first).

* If something doesn't work as it should, let us know (specifically, concentrate on correct load paths, encodings, changes in binary extensions and also other new features added between 1.8.7 and 1.9.3).

* If something doesn't work as it should, let us know (specifically, concentrate on correct load paths, encodings, changes in binary extensions and also other new features added between 1.8.7 and 1.9.3).

Line 128:

Line 128:

** Ruby libraries managed by RPM are now installed into vendor directories while other libraries managed by system administrator should go into site directories.

** Ruby libraries managed by RPM are now installed into vendor directories while other libraries managed by system administrator should go into site directories.

−

* http://svn.ruby-lang.org/repos/ruby/tags/v1_8_7_357/NEWS

+

* http://svn.ruby-lang.org/repos/ruby/tags/v1_8_7_374/NEWS

* http://svn.ruby-lang.org/repos/ruby/tags/v1_9_1_431/NEWS

* http://svn.ruby-lang.org/repos/ruby/tags/v1_9_1_431/NEWS

−

* http://svn.ruby-lang.org/repos/ruby/tags/v1_9_2_290/NEWS

+

* http://svn.ruby-lang.org/repos/ruby/tags/v1_9_2_320/NEWS

−

* http://svn.ruby-lang.org/repos/ruby/tags/v1_9_3_0/NEWS

+

* http://svn.ruby-lang.org/repos/ruby/tags/v1_9_3_448/NEWS

+

* http://svn.ruby-lang.org/repos/ruby/tags/v2_0_0_247/NEWS

== Comments and Discussion ==

== Comments and Discussion ==

Line 138:

Line 139:

−

[[Category:FeatureReadyForFesco]]

+

[[Category:FeatureAcceptedF17]]

<!-- When your feature page is completed and ready for review -->

<!-- When your feature page is completed and ready for review -->

<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->

<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->

<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->

<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->

<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Ruby 1.9.3 is the latest stable version of Ruby, with major increases in speed and reliability. With this major update from Ruby 1.8.7 in Fedora 16 to Ruby 1.9.3 in Fedora 17, alongside JRuby, Fedora becomes the superior Ruby development platform.

Ruby 1.9.3 is upstream's new major release of Ruby. The MRI reference interpreter is replaced by the YARV bytecode interpreter, designed to greatly improve the execution time of ruby programs. [1]

In doing so, upstream has set the anticipations for downstream consumers with faster and more reliable Ruby. Bringing Ruby 1.9.3 to Fedora is essential for Fedora to be at the top of it's game as a Ruby development platform.

Requires rebuilding numerous packages that depend on ruby(abi) = 1.8, or have Requires or BuildRequires for package dependent on ruby(abi) = 1.8. All these packages have to be updated to support ruby(abi) = 1.9

Use the packages, ideally with your applications previously written in Ruby (be sure to upgrade your applications to Ruby 1.9.3 first).

If something doesn't work as it should, let us know (specifically, concentrate on correct load paths, encodings, changes in binary extensions and also other new features added between 1.8.7 and 1.9.3).

Please note that we already tested all packages available in Fedora for compatibility with Ruby 1.9.3. You can go through the findings in following mailing list threads:

We would like to get a special buildroot tag to be able to rebuild all the packages with Ruby 1.9.3. If anything goes wrong, the tag could be easily dropped and previous version of Ruby 1.8.7 and its dependencies stays intact.

The Ruby 1.9.3 breaks ABI/API compatibility with previous version of Ruby, therefore soname was bumped. All RubyGems which use binary extensions should be rebuilt. All applications which use Ruby binding should be rebuilt.

Ruby 1.9.3 as well as integrated version of RubyGems now use different directory structure, compatible with FHS. All libraries need to be adjusted to this change. This change is reflected in new packaging guidelines draft.

Unprivileged user now installs gems automatically into her/his home directory, root installs gems into /usr/local directory structure and system gems, managed by RPM, are installed into /usr.

Ruby libraries managed by RPM are now installed into vendor directories while other libraries managed by system administrator should go into site directories.