During review of rubygem-spring  I discovered, that RubyGems 2.1+
carries new "secrete" feature, which is used by spring pre-loader and
that is "stub specification" . If this stub support is not available
in .gemspec file, the spring prints following error:
Warning: Running `gem pristine --all` to regenerate your installed
(and deleting then reinstalling your bundle if you use bundle --path)
improve the startup performance of Spring.
Hence gems, which were already build against RubyGems 2.1+ (i.e. every
gem build in F20+ approx. since 2013-10-21) should be ready. All other
gems might need rebuild to get rid of this warning.
Fortunately, I suppose there will be Fedora mass-rebuild prior F21, so
no action should be needed. But I though it might be interesting
Dne 18.3.2014 10:55, Vít Ondruch napsal(a):
We would like to update RoR in Fedora to the RoR 4.1, which are close
release. Sorry for the late notice.
-------- Původní zpráva --------
Předmět: F21 System Wide Change: Ruby on Rails 4.1
Datum: Tue, 18 Mar 2014 10:43:49 +0100
Od: Jaroslav Reznik <jreznik(a)redhat.com>
Přeposláno - Komu: devel(a)lists.fedoraproject.org
Společnost: Red Hat, Inc.
= Proposed System Wide Change: Ruby on Rails 4.1 =
Change owner(s): Vít Ondruch <vondruch(a)redhat.com>, Josef Stříbný
Ruby on Rails 4.1 is the latest version of well know web framework written in
== Detailed Description ==
The Ruby on Rails stack is evolving quickly and Fedora needs to keep pace with
it. Therefore the whole Ruby on Rails stack should be updated from 4.0 in
Fedora 20 to 4.1 (latest version) in Fedora 21. This will ensure that all the
Ruby developers using Fedora have the latest and greatest RPM-packaged Ruby on
== Scope ==
* Proposal owners:
** The whole Rails stack has to be updated
** Some dependencies of the Rails stack will need update
For the list of packages that need to be created/updated, see the Change Page.
* Other developers: Update Rails dependent packages to be working with Ruby on
* Release engineering: Not needed.
* Policies and guidelines: Not needed
devel-announce mailing list
ruby-sig mailing list