Ruby 2.2
by Vít Ondruch
Hi everybody,
Since Ruby 2.2 is going to be released during Christmas and -preview1
release is imminent (this Wednesday?), it is probably time to start
looking into its packaging. So here is the updated .spec file [1] and
scratch build [2], which can be finally build on all platforms. Sorry,
no Copr for you, since Ruby's build fails there due to old RHEL kernel :/.
What has changed from packaging point of view? Luckily, not much, but
here are a few bullets which comes to my mind:
* RPM 4.12 introduces new %load function, which is used to load RPM
macros during RPM build. This allowed to drop my custom RPM macro [3].
On the other hand, you'll be able to build the Ruby only on F21+
(luckily, you should be able to build SRPM everywhere).
* The RubyGems filesystem was not explicit enough, so there might be
something accidentally packages. This is now more explicit, so we should
be safer.
* Ruby now ships with MiniTest and Test::Unit. The very good news is
that they are installed so far as a regular gems. This means that you
have to always specify them in your Gemfile, if you are using Bundler,
but this is generally step in good direction. I hope that upstream will
not change their mind :) Due to this change, we have new subpackages
rubygem-test-unit (and rubygem-power_assert, which is now Test::Unit's
dependency). No more %{_bindir}/testrb (but nobody is using it these
days anyway, right? ;)
* Some prevailing test failures were resolved, some others introduced,
but hopefully they'll get resolved prior stable release.
Generally, I'd say that not much has changed since 2.1, which is good news.
Please test the packaging if you can and let me know about any issues
you encountered.
Also, if you have any other suggestions about Ruby packaging in general,
what we could improve etc, this is probably good time to share. It seems
that OpenSUSE guys are improving their packaging, so you might want to
get some inspiration there [4, 5, 6] ;)
Vít
[1] http://pkgs.fedoraproject.org/cgit/ruby.git/log/?h=private-ruby-2.2
[2] http://koji.fedoraproject.org/koji/taskinfo?taskID=7578843
[3]
http://pkgs.fedoraproject.org/cgit/ruby.git/commit/?h=private-ruby-2.2&id...
[4] https://build.opensuse.org/package/show/home:darix:ruby/ruby-common
[5] https://build.opensuse.org/package/show/home:darix:ruby/ruby2.2
[6] https://github.com/openSUSE/gem2rpm/commits/master
8 months
un-retire rubygem-factory_girl
by Vít Ondruch
Hi,
rubygem-factory_girl was retired during march since it was orphaned for
some while. I did not picked it up at that time, since nothing was using
it. Now I discovered that it would be handy to have it in Fedora to be
able to execute test suite of rubygem-cucumber-rails. Hence I inted to
un-retire it. Here is the re-review request:
https://bugzilla.redhat.com/show_bug.cgi?id=1470580
Thx
Vít
6 years, 10 months
[ANN] ruby-sig and ruby-packagers-sig groups
by Vít Ondruch
Hi everybody,
As I promised earlier [1], the ruby-sig and ruby-packagers-sig were
established, together with ruby-packagers-sig mailing list [2]. Not sure
precisely how this is going to pan out, but lets try this:
1) I would appreciate if we can transform the list of SIG members [3]
into the ruby-sig FAS group. Therefore, can I ask interested parties to
apply for this group in FAS? As soon as you apply, I will sponsor you
and I'll select a few of you as additional sponsors. Not sure what
should be the mininal level to sponsor members, but the bar shouldn't be
high. May be introduction on ruby-sig ML together with ruby package
review could suffice ...
2) Any of you who is maintaining some interesting package should think
about (a) adding ruby-packagers-sig group as a administrator of the
package (b) consider moving the ownership of the package to
ruby-packages-sig (but please I hope it won't end up just as a junkyard
of packages you don't have time to maintain anymore ;) ). As of
membership in ruby-packagers-sig, I propose that the minimal level for
sponsoring into this group should be maintenance of 5 ruby related
package and be packager at least 1 year (possibly with some exception,
especially for full time maintainers).
Any thoughts, suggestions, comments?
BTW, anybody willing to request badges for being member of Ruby-SIG? ;)
Vít
[1]
https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraprojec...
[2] https://pagure.io/fedora-infrastructure/issue/5478
[3] https://fedoraproject.org/wiki/SIGs/Ruby#Members
6 years, 10 months