Based on my discussions with the community and various parties that
have a vested interest in this, I feel that it is a good idea to move
the rubygem-rails packages to rails 3.0.x for F15 so that we don't get
left behind and stay up to date w/ the latest / greatest upstream releases.
Unfortunately this process isn't as simple as updating the 6 rails
packages (rails itself and the active/action* packages), there are many
various gems which will need to be updated as well to work with Rails 3.
Based on my findings w/ deltacloud [1], the update process itself isn't
so difficult, but some of the following gems will need to be updated in
Fedora for things to properly work. Most likely more will need to be as
well, these are just the ones that I've found, but conversely all of
these may not need to be updated, as I installed Rails 3 via gem which
pulled in the latest version of all these packages.
* rails, activesupport, activerecord, actionpack, activeresource, actionmailer - 2.3.8 -> 3.0.1 (mmorsi)
* compass - 0.8.17 -> 0.10.6 (mmorsi)
* cucumber - 0.9.0 -> 0.9.3 (kanarip, mfojtik, mkent, stahnma)
* erubis - 2.6.5 -> 2.6.6 (mkent)
* gherkin - 2.2.4 -> 2.2.9 (mfojtik)
* haml - 3.0.17 -> 3.0.23 (mkent, kanarip)
* polyglot - 0.2.5 -> 0.3.1 (kanarip, stahnma)
* rack - 1.1.0 -> 1.2.1 (kanarip, stahnma)
* rack-test - 0.5.4 -> 0.5.6 (mfojtik)
* rspec - 1.3.0 -> 2.0.1 (stahnma)
* simple-navigation - 3.0.0 -> 3.0.2 (mfojtik)
* sinatra - 1.0 -> 1.1.0 (mfojtik)
* sqlite3-ruby - 1.2.4 -> 1.3.2 (kanarip, stahnma)
* term-ansicolor - 1.0.3 -> 1.0.5 (hpejakle, mfojtik)
* thor - 0.13.6 -> 0.14.3 (mkent)
* treetop - 1.3.0 -> 1.4.8 (stahnma)
Also the following are new gems which will need to be packaged
* arel (1.0.1)
* autotest (4.4.2)
* bundler (1.0.3)
* database_cleaner (0.6.0)
* factory_girl_rails (1.0)
* i18n (0.4.2)
* mail (2.2.29)
* tilt (1.1)
* timecop (0.3.5)
* rack-mount (0.6.13)
* railties (3.0.1)
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
* tzinfo (0.3.23)
In the upcoming weeks (most likely starting after the new year) I will
be looking to updating the rails packages themselves and coordinating
updates with the owners of these gems. I also think it might be a good
idea to submit a feature request for Fedora 15 for Rails 3.
Thoughts, comments, and help with any and all of this would be very much
appreciated. Thanks alot.
-Mo
[1] http://mo.morsi.org/blog/node/331
Hey all, since there have been no objections so far, I'm going to be
pushing the updates to the first Rails 3 dependencies rubygem treetop
(1.4.9) and thor (0.14.6) to rawhide tonight.
I'm also going to be getting back to the packages that I reviewed that
have since been updated. I ask that anyone whose package I reviewed in
the context of rails 3 please get back to my feedback as soon as you
can. Also I still could use a few reviewers to take one or two packages
from the list of new ones I submitted. There are pretty simple /
non-controversial, and it shouldn't take long at all to get through those.
To see the list of packages I've reviewed and those I need a reviewer
for, see my last Rails 3 email thread
http://lists.fedoraproject.org/pipermail/ruby-sig/2011-January/000416.html
Thanks alot,
-Mo
Hello,
Currently I am dealing with several rubygems (arel, regin) that do not
contain bundled their test suites, although the test suite is usually
available on GitHub. It would be nice to run the test suite during
packaging, however I am reluctant to modify the package in that way that
it will include the test suite.
So here is my proposal:
# Preparation of the test suite
# git clone http://github.com/somerepo/somegem.git
# cd somegem/
# tar czvf somegem-tests.tgz spec/
Source1: some-tests.tgz
%check
mkdir %{_tmppath}/%{gemname}-%{version}
tar xzvf %{SOURCE1} -C %{_tmppath}/%{gemname}-%{version}
pushd %{_tmppath}/%{gemname}-%{version}
ruby -I%{buildroot}%{geminstdir}/lib `which spec` spec
popd
rm -rf %{_tmppath}/%{gemname}-%{version}
What is your opinion?
Vit