- 1 Ruby 2.0.0
- 1.1 Summary
- 1.2 Owner
- 1.3 Current status
- 1.4 Detailed Description
- 1.5 Benefit to Fedora
- 1.6 Scope
- 1.7 How To Test
- 1.8 User Experience
- 1.9 Dependencies
- 1.10 Contingency Plan
- 1.11 Documentation
- 1.12 Release Notes
- 1.13 Comments and Discussion
Ruby 2.0.0 is the latest stable version of Ruby, with major increases in speed and reliability. With this major update from Ruby 1.9.3 in Fedora 18 to Ruby 2.0. in Fedora 19, alongside JRuby, Fedora becomes the superior Ruby development platform.
- Name: Vít Ondruch
- Email: email@example.com
- Targeted release: Fedora 19
- Last updated: 2013-01-07
- Percentage of completion: 10%
Ruby 2.0.0 is upstream's new major release of Ruby. It caries new features such as:
- Keyword arguments
- #to_h: Convention for conversion to Hash
- %i: a literal for symbol array
- regexp engine was changed to Onigmo
- DTrace support
Yet, it is source level backward compatible with Ruby 1.9.3, so you will continue to work.
The updated Ruby also provides better integration with Fedora, especially JRuby. But not only JRuyb, it is also one step closer to be prepared for other interpreters, such as Rubinius. Providing of custom Ruby loader with working name "multiruby"  will allow to easily switch interpreters executing your script, provides fallback to whatever Ruby interpreter is available on you system, yet still keeps backward compatibility with all your Ruby scripts.
Benefit to Fedora
Supporting the growth of a Ruby language with a latest release supporting the newest language features, which enables even faster and easier development of Ruby applications. Add to that the multiplatform targetted development we enable downstream parties to do using our distribution.
The following list includes a summary of changes included in this feature:
- New Packaging Guidelines for Ruby packages (different virtual provide semantics, native extensions moved into different directory). This has to be done in sync with JRuby related changes to packaging guidelines.
- Rebuilding of all Ruby packages, and all packages depending on Ruby
- Changes to the search path to comply with the multi-versioning
How To Test
New Packaging Guidelines
Drafts of new packaging guidelines will have to be proposed to FPC. You can see the current draft.
Packages that require "ruby(abi) = 1.9.1"
Requires rebuilding numerous packages that depend on ruby(abi) = 1.9.1, or have Requires or BuildRequires for package dependent on ruby(abi) = 1.9.1. All these packages have to be updated to support new virtual provides.
- 211 in total
repoquery --repoid=rawhide-source --arch=src --whatrequires 'ruby(abi) = 1.8' | sort | uniq
Packages that require "*ruby*"
- 452 in total (211 matches from previous query, of course)
repoquery --repoid=rawhide-source --arch=src --whatrequires '*ruby*' | sort | uniq
- The Ruby 2.0.0 breaks ABI 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. Nevertheless, since upstream payed great attention to source compatibility, no changes to your code are needed.
- RubyGems with binary extensions now use different directory structure, to provide better compatibility with JRuby and other interpreters. All libraries need to be adjusted to this change. This change is reflected in new packaging guidelines draft.
Comments and Discussion
- See Talk:Features/Ruby 2.0.0 or Ruby-SIG mailing list.