conflicting guidelines
by Mo Morsi
Hey was just look at the updated guidelines here [1] (if there is a more
recent version, please let me know).
I was a bit thrown off by the following two guidelines:
- Under 'Ruby Compatibility'
"Each Ruby package *must* indicate it depends on a Ruby interpreter. Use
ruby(release) virtual requirement to achieve that: Requires: ruby(release)"
- Under "Libraries" > "Rubygems"
"There *should* not be |Requires: ruby(release)|, unless you want to
explicitly specify Ruby version compatibility. Automatically generated
dependency on RubyGems (|Requires: ruby(rubygems)|) is enough."
Should the former only take effect for non-gem Ruby packages?
-Mo
[1] https://fedoraproject.org/w/index.php?title=PackagingDrafts%2FRuby
9 years, 12 months
Minitest 5 update
by Josef Stribny
Hi Rubyists,
as you have probably noticed we would like to update Rails framework to the latest version (4.1) when it's released[1].
The biggest task for us in this change is the update of Minitest to version 5. This would require test suites
of many gems that depends on Minitest to be fixed.
Here are the most significant changes of Minitest 5 taken from the changelog[2]:
* 12 major (oft incompatible) changes:
* Renamed MiniTest to Minitest. Your pinkies will thank me. (aliased to MiniTest)
* Removed MiniTest::Unit entirely. No more manager objects.
* Added Minitest::Runnable. Everything minitest can run subclasses this.
* Renamed MiniTest::Unit::TestCase to Minitest::Test (subclassing Runnable).
* Added Minitest::Benchmark.
* Your benchmarks need to move to their own subclass.
* Benchmarks using the spec DSL have to have "Bench" somewhere in their describe.
* MiniTest::Unit.after_tests moved to Minitest.after_tests
* MiniTest::Unit.autorun is now Minitest.autorun. Just require minitest/autorun pls.
* Removed ParallelEach#grep since it isn't used anywhere.
* Renamed Runnable#__name__ to Runnable#name (but uses @NAME internally).
* Runnable#run needs to return self. Allows for swapping of results as needed.
That means the minimal changes needed to be done for every minitest test suite include:
* rename MiniTest::Unit::TestCase to Minitest::Test
* change require 'minitest/unit' (or 'test/unit') to require 'minitest/autorun'
* delete MiniTest::Unit.autorun (or use Minitest.autorun)
For some really simple test suites that might be enough. Look at the changes done in Rails 4.1[3]
or in my own little gem[4] for how the necessary changes may look like. For the others some additional
changes might be required.
Another problem are gems that depends on Gem::TestCase (like RubyGems plugins)
since Gem::TestCase is inherited from MiniTest::Unit::TestCase. I guess this can't be easily
solved at the moment, but we probably don't have many gems like that, or are we?
So what do you think of this change? Should we address it by updating upstream test suites?
Do you know about other issues that this can cause and I forgot to mention?
Josef
[1] https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_4.1
[2] https://github.com/seattlerb/minitest/blob/master/History.txt#L137
[3] https://github.com/rails/rails/commit/3073c531983de243219fb55be93fbcebfdd...
[4] https://github.com/strzibny/ruby-ares/commit/a1017ce59eeb8bfb5256b6e7789d...
9 years, 12 months
Xml persistent
by Sayth Renshaw
Has anyone good advice or know of a rails/activerecord module for uploading
xml to database automatically.
So my xml files will be same structure and hoping that I could set it up so
others can just drop in the xml themselves.
Sayth
9 years, 12 months
Orphaning my rubygems
by Bohuslav Kabrda
Hi all,
since I no longer have time to work on Fedora's Ruby stack, I'm orphaning all my rubygems, feel free to take them:
rubygem-ammeter
rubygem-apipie-rails
rubygem-aruba
rubygem-bacon
rubygem-coffee-rails
rubygem-coffee-script
rubygem-color
rubygem-delorean
rubygem-excon
rubygem-execjs
rubygem-fog
rubygem-formatador
rubygem-gettext_i18n_rails
rubygem-haml-rails
rubygem-jquery-rails
rubygem-ldap_fluff
rubygem-little-plugger
rubygem-logging
rubygem-map
rubygem-net-ldap
rubygem-openstack-compute
rubygem-pry
rubygem-ruby-dbus
rubygem-ruby-libvirt
rubygem-shindo
rubygem-sinatra
rubygem-slop
rubygem-sprockets
rubygem-temple
rubygem-test_declarative
rubygem-therubyracer
rubygem-uglifier
They'll be available in few minutes from now.
Enjoy :)
Slavek
10 years
Ruby on Rails 4.1 landed in Fedora
by Josef Stribny
Hi all fellow rubyists,
I am pleased to announce that we now have the latest version of the Ruby on Rails framework (4.1)
packaged in Fedora[1, 2]. You may have noticed we did the update alongside the Ruby 2.1 rebuild
as this was the most convenient.
The big success for us is the usage of the new version of tzinfo gem which by default depend on
the system zoneinfo files. Other notable changes are Minitest 5 (which we already discussed) and
the new gems rubygem-actionview and rubygem-spring.
Today I updated depending gems that are compatible with Rails 4.1 in their latest versions[3].
Those that don't support newest Rails yet remain broken. If I forgot on any gem, please remind me.
You can install rails and the default gems from the newly-generated Gemfile by running*:
`yum install rubygem-{rails,sqlite3,coffee-rails,sass-rails,uglifier,jquery-rails,turbolinks,jbuilder,therubyracer,sdoc,spring}`
Afterwards,
`rails new _app_ --skip-bundle && cd _app_ && bundle --local`
will avoid the need of downloading upstream gems.
And this brings me to another great thing. By updating to the latest RubyGems we got a working
upstream version of Bundler which means updating Bundler by `gem update bundler` is now safe && sane!
Hope you will like the changes as much as I do :).
Happy Weekend
Josef
* if it fails on sdoc, please wait some time until the newest build is available
[1] https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_4.1
[2] http://guides.rubyonrails.org/4_1_release_notes.html
[3] https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_4.1#Dependencies
10 years
