From Fedora Project Wiki
< Features
(Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To ...") |
No edit summary |
||
| Line 11: | Line 11: | ||
<!-- The actual name of your feature page should look something like: Features/Your_Feature_Name. This keeps all features in the same namespace --> | <!-- The actual name of your feature page should look something like: Features/Your_Feature_Name. This keeps all features in the same namespace --> | ||
= | = Features/JRuby 1.7.1 = | ||
== Summary == | == Summary == | ||
JRuby is an alternative Ruby implementation with fast growing user base due to its great performance in parallel tasks. Although JRuby 1.6.7 is already in Fedora, this feature brings in new major version and better Fedora integration. | |||
== Owner == | == Owner == | ||
* Name: [[User:Bkabrda| Bohuslav Kabrda]] | |||
* Name: [[User: | |||
* Email: <bkabrda@redhat.com> | |||
* Email: < | |||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/19 | Fedora 19 ]] | ||
* Last updated: | * Last updated: 2012-12-3 | ||
* Percentage of completion: | * Percentage of completion: 5% | ||
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | <!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. --> | ||
== Detailed Description == | == Detailed Description == | ||
Transition to JRuby 1.7.1 will consist of 3 basic steps: | |||
* Updating packages | |||
** Most of the packages that JRuby depends on are in Fedora just because of JRuby, so they can be safely updated. | |||
** Some dependencies are shared with other packages, so they will have to be discussed with their owners (TODO: list). | |||
* Integration with Fedora | |||
** Normally, each Ruby implementations ships with its own copy of RubyGems library. This is wrong because a) it's bundling, b) there is no reason why multiple Ruby implementations wouldn't be able to share one RubyGems library. There used to be some differencies in JRuby's copy of RubyGems, but the JRuby upstream has been very cooperative and managed to get them all merged into upstream RubyGems. | |||
** The integration will require changing Fedora's operating_system.rb (place for distro-specific defaults for RubyGems). This change will result into all Gems with binary extensions having to be recompiled, as the binary extension placement will change. See [1] for current operating_system.rb look and its changes from F18. | |||
** TODO: /usr/bin/ruby stub | |||
* Changes in packaging | |||
** This feature will require some additions to Ruby Packaging Guidelines, the draft can be seen at TODO: pg_draft. | |||
** An example of RubyGem packaged with both C and Java extension can be seen at [2]. | |||
[1] https://github.com/bkabrda/jruby.spec/blob/master/rubygems/operating_system.rb | |||
[2] https://github.com/bkabrda/jruby.spec/blob/master/rubygem-json/rubygem-json.spec | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
JRuby is starting to get very popular among Rubyists, mainly because of its excelent performance in tasks using concurrency (leveraging power of JVM). Because of this, JRuby is mainly used for running web (mostly Ruby on Rails) applications under great stress. Having up-to-date and sanely packaged JRuby is a must for Ruby development and deployment platform. | |||
== Scope == | == Scope == | ||
The changes only affect Ruby packages in Fedora. Few updated Java packages (TODO:) may also affect some Java packages - this will have to be discussed with their owners. | |||
== How To Test == | == How To Test == | ||
| Line 53: | Line 64: | ||
3. What are the expected results of those actions? | 3. What are the expected results of those actions? | ||
--> | --> | ||
1) There is a testing repo at http://bkabrda.fedorapeople.org/jruby/jruby.repo, which can be used to test. Do not install this on your system, due to the changes mentioned above, it would break your standard Ruby installation. This repo is meant to be tested in fedora-19-x86_64 mock chroot, where it can do no harm. | |||
2) The repo packages do not contain all the integration features mentioned above, but provide a functional and usable JRuby installation. | |||
== User Experience == | == User Experience == | ||
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
JRuby will be up-to-date, usable and will be able to use Fedora's RPM-packaged RubyGems. | |||
== Dependencies == | == Dependencies == | ||
As mentioned, few Java packages, that are dependencies of some other packages, will have to be updated (TODO:). Also, all the RubyGems packages with binary extensions will have to be rebuilt (TODO:). | |||
== Contingency Plan == | == Contingency Plan == | ||
Reverting to the previous behaviour will always be doable very easily, no harm will be done. | |||
== Documentation == | == Documentation == | ||
<!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | <!-- Is there upstream documentation on this feature, or notes you have written yourself? Link to that material here so other interested developers can get involved. --> | ||
* | * https://github.com/bkabrda/jruby.spec | ||
* Discussions on Fedora's ruby-sig mailing list for last few months (http://lists.fedoraproject.org/pipermail/ruby-sig/). | |||
== Release Notes == | == Release Notes == | ||
<!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | <!-- The Fedora Release Notes inform end-users about what is new in the release. Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ --> | ||
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | <!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the documentation team and shipped with the release. --> | ||
* | * Upstream release notes at http://jruby.org/2012/10/22/jruby-1-7-0.html | ||
== Comments and Discussion == | == Comments and Discussion == | ||
Revision as of 12:52, 3 December 2012
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
Set a Page Watch
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
Make sure you click watch on your new page so that you are notified of changes to it by others, including the Feature Wrangler
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed
Features/JRuby 1.7.1
Summary
JRuby is an alternative Ruby implementation with fast growing user base due to its great performance in parallel tasks. Although JRuby 1.6.7 is already in Fedora, this feature brings in new major version and better Fedora integration.
Owner
- Name: Bohuslav Kabrda
- Email: <bkabrda@redhat.com>
Current status
- Targeted release: Fedora 19
- Last updated: 2012-12-3
- Percentage of completion: 5%
Detailed Description
Transition to JRuby 1.7.1 will consist of 3 basic steps:
- Updating packages
- Most of the packages that JRuby depends on are in Fedora just because of JRuby, so they can be safely updated.
- Some dependencies are shared with other packages, so they will have to be discussed with their owners (TODO: list).
- Integration with Fedora
- Normally, each Ruby implementations ships with its own copy of RubyGems library. This is wrong because a) it's bundling, b) there is no reason why multiple Ruby implementations wouldn't be able to share one RubyGems library. There used to be some differencies in JRuby's copy of RubyGems, but the JRuby upstream has been very cooperative and managed to get them all merged into upstream RubyGems.
- The integration will require changing Fedora's operating_system.rb (place for distro-specific defaults for RubyGems). This change will result into all Gems with binary extensions having to be recompiled, as the binary extension placement will change. See [1] for current operating_system.rb look and its changes from F18.
- TODO: /usr/bin/ruby stub
- Changes in packaging
- This feature will require some additions to Ruby Packaging Guidelines, the draft can be seen at TODO: pg_draft.
- An example of RubyGem packaged with both C and Java extension can be seen at [2].
[1] https://github.com/bkabrda/jruby.spec/blob/master/rubygems/operating_system.rb [2] https://github.com/bkabrda/jruby.spec/blob/master/rubygem-json/rubygem-json.spec
Benefit to Fedora
JRuby is starting to get very popular among Rubyists, mainly because of its excelent performance in tasks using concurrency (leveraging power of JVM). Because of this, JRuby is mainly used for running web (mostly Ruby on Rails) applications under great stress. Having up-to-date and sanely packaged JRuby is a must for Ruby development and deployment platform.
Scope
The changes only affect Ruby packages in Fedora. Few updated Java packages (TODO:) may also affect some Java packages - this will have to be discussed with their owners.
How To Test
1) There is a testing repo at http://bkabrda.fedorapeople.org/jruby/jruby.repo, which can be used to test. Do not install this on your system, due to the changes mentioned above, it would break your standard Ruby installation. This repo is meant to be tested in fedora-19-x86_64 mock chroot, where it can do no harm. 2) The repo packages do not contain all the integration features mentioned above, but provide a functional and usable JRuby installation.
User Experience
JRuby will be up-to-date, usable and will be able to use Fedora's RPM-packaged RubyGems.
Dependencies
As mentioned, few Java packages, that are dependencies of some other packages, will have to be updated (TODO:). Also, all the RubyGems packages with binary extensions will have to be rebuilt (TODO:).
Contingency Plan
Reverting to the previous behaviour will always be doable very easily, no harm will be done.
Documentation
- https://github.com/bkabrda/jruby.spec
- Discussions on Fedora's ruby-sig mailing list for last few months (http://lists.fedoraproject.org/pipermail/ruby-sig/).
Release Notes
- Upstream release notes at http://jruby.org/2012/10/22/jruby-1-7-0.html