Changes/Ruby193 in SCL
Ruby193 in SCL
Ruby 1.9.3 with Rails 3.2.8 is still commonly used by many projects. Let's provide Ruby and Rails in SCL even for Fedora. Rails depends on exact v8 version, which means v8 3.14 must have also their own SCL as part of the SCL.
- Name: MarcelaMašláňová
- Email: email@example.com
- Release notes owner:
- Responsible WG: Env and Stacks WG
- Targeted release: Fedora 21
- Last updated: 7. 4. 2014
- Tracker bug: <will be assigned by the Wrangler>
Ruby 1.9.3 with Rails 3.2.8 is still commonly used by many projects. This change aims to provide Ruby 1.9.3 and Rails 3.2.8. Rails depends on exact v8 version, which means v8 3.14 must have also their own SCL as part of this change.
Benefit to Fedora
All application dependent on older Ruby and Rails can run happily. Ruby SCL was picked, because many Cloud projects is still dependent on older version of Rails. It would be wise to provide them Fedora, where they can develop their application without being pushed to maintain apps on various Rails releases.
- Proposal owners: Marcela
- create the actual collections, at start in Copr and on SCL upstream
- Other developers: Cloud WG
- test SCL with their apps
- Release engineering:
- create branches in dist-git
- add Ruby193 packages into compose
Ruby193 will be installed outside of the regular system. No problem for system packages.
How To Test
0. Install SCL
1. Run your favourite application on the collection
eg. scl enable ruby193 'foreman'
0. Install SCL
1. Create your own application for older version of language (change shebang in your script to /opt/fedora/ruby193/...)
Two major use-cases:
- developers will develop their apps - they will need to change shebang of application for example from /usr/bin/ruby to something like /opt/fedora/ruby/...
- users of apps, which already depend on SCL, can happily use their app, which is finally working
- create one SCL
- co-operate with relengs
- branches in dist-git
- modify buildroot (add into minimal buildroot scl-utils and scl-utils-build) - it might be valid only for packages for specific branches
- FPC ticket
- Contingency mechanism: If something went bad, we could still use Copr repository for providing SCL.
- Contingency deadline: 1.7.2014
- Blocks release? No.
- Blocks product? Yes, it might block Cloud WG if they depend on Ruby193.
There will be a process documentation in form of wiki pages. User documentation already exists.
Documentation of the collection will be provided as soon as collection is ready.