ruby-sig March 2014

ruby-sig@lists.fedoraproject.org

7 participants
8 discussions

BASH completion for Ruby
by Vít Ondruch 25 May '16

25 May '16

Hi guys, Anybody have any experience with some scripts for bash completion? Have you tried any? Should we integrate any? Just a quick googling gave me two results: https://github.com/mernen/completion-ruby https://github.com/pdkl95/rubygems-completion And there are probably others. I did not tried them yet. Have you? Do you have other/better tips? Thank you Vit

2 3

Minitest 5 update
by Josef Stribny 26 May '14

26 May '14

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/3073c531983de243219fb55be93fbcebfdd9c… [4] https://github.com/strzibny/ruby-ares/commit/a1017ce59eeb8bfb5256b6e7789d95…

4 13

Updating bundler in EPEL6
by Mo Morsi 22 Apr '14

22 Apr '14

Greetings, there are a couple of bugs [1] [2] filed against the outdated version of rubygem-bundler in EPEL. Looking at the bundler changelog [3], I do not see any noticeable regressions / deprecations since the version we currently ship via el6 (1.1.4) so this update should be fine w/ the EPEL update policy [4]. I've updated my local spec to the version in rawhide (1.5.2) and have run a working scratch build against the el6-candidate [5]. Are there any objections to proceeding with this? If not I'll run the update sometime next week. Take care, -Mo [1] https://bugzilla.redhat.com/show_bug.cgi?id=908061 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1078539 [3] https://github.com/bundler/bundler/blob/master/CHANGELOG.md [4] https://fedoraproject.org/wiki/EPEL_Updates_Policy [5] http://koji.fedoraproject.org/koji/taskinfo?taskID=6680738

2 4

GitLab unofficial meeting
by Achilleas Pipinellis 22 Mar '14

22 Mar '14

Hey guys, This Thursday March 20 (tomorrow that is :) ), after the Infrastructure meeting (18:00-19:00 UTC) we are gonna hijack on #fedora-admin and hold an unofficial meeting on GitLab, since many folks have expressed interest on its current status in Fedora/EPEL. Sytse Sijbrandij, co-founder of GitLab, will be there as well to discuss the potential of deploying GitLab in Fedora or Red Hat infrastructure. It would be cool if guys from Fedora infra team or anyone inside Red Hat could attend (cc'ing some of you that reached me). Sorry for the late notice, I've been somewhat busy lately, if someone cannot make it we can always arrange to meet next week as well. So see you tomorrow on #fedora-admin at 19:00 UTC. -- FAS : axilleas GPG : 0xABF99BE5 Blog: http://axilleas.me

2 2

Packaging guidelines for F21
by Vít Ondruch 20 Mar '14

20 Mar '14

Hi, I am working on draft of Ruby packaging guidelines for F21 [1]. The main two changes are: 1) Simplified packaging of binary extensions (although there is still one caveat [2]). 2) Changes due to automatic dependency generators. If you have any comments, suggestions, please let me know. Vít [1] https://fedoraproject.org/w/index.php?title=PackagingDrafts%2FRuby&diff=372… [2] https://lists.fedoraproject.org/pipermail/ruby-sig/2014-January/001484.html

3 6

Fwd: F21 System Wide Change: Ruby on Rails 4.1
by Vít Ondruch 18 Mar '14

18 Mar '14

We would like to update RoR in Fedora to the RoR 4.1, which are close to release. Sorry for the late notice. Vít -------- 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. Komu: devel-announce(a)lists.fedoraproject.org = Proposed System Wide Change: Ruby on Rails 4.1 = https://fedoraproject.org/wiki/Changes/Ruby_on_Rails_4.1 Change owner(s): Vít Ondruch <vondruch(a)redhat.com>, Josef Stříbný <jstribny(a)redhat.com>, ruby-sig(a)lists.fedoraproject.org Ruby on Rails 4.1 is the latest version of well know web framework written in Ruby. == 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 Rails. == 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 Rails 4.1 * Release engineering: Not needed. * Policies and guidelines: Not needed _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce

1 1

Re: F21 System Wide Change: Ruby 2.1
by Vít Ondruch 13 Mar '14

13 Mar '14

Dne 13.3.2014 10:43, Jaroslav Reznik napsal(a): > ----- Original Message ----- >> = Proposed System Wide Change: Ruby 2.1 = >> https://fedoraproject.org/wiki/Changes/Ruby_2.1 >> >> Change owner(s): Vít Ondruch <vondruch(a)redhat.com> >> >> Ruby 2.1 is the latest stable version of Ruby, with major increases in speed, >> memory efficiency and reliability. With this major update from Ruby 2.0.0 in >> Fedora 20 to Ruby 2.1 in Fedora 21, alongside JRuby, Fedora becomes the >> superior Ruby development platform. > This Change was approved by FESCo on yesterdays meeting with a note: "this > requires a mini-mass rebuild for native ruby extensions so schedule needs > to account for that". > > Jaroslav Just for the record, bellow is the list of packages (147) which will need rebuild, obtained using: $ repoquery --disablerepo=* --enablerepo=rawhide --enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel' | sort | uniq The rubygem-* packages will need some changes, which you can apply by: https://github.com/voxik/fermig/blob/master/update.rb Let me know if you'd prefer to do the rebuild yourself, otherwise I'll rebuild your package. But prior the rebuild happens, I need to submit updated guidelines to FPC and I'll try to ask rel-eng for side tag, so this probably won't start sooner than 24th of March (date change reserved ;). Vít alexandria chipmunk clearsilver condor-wallaby eruby facter fantasdic gdal graphviz hiera hivex hyperestraier ice kazehakase libcaca libdmtx libguestfs libselinux libsolv libyui-bindings marisa mcollective migemo mingw-qpid-cpp obexftp openbabel openshift-origin-broker-util openwsman pcs player postgresql-plruby psi4 puppet qdbm qpid-qmf redland-bindings remctl root rrdtool ruby-RMagick ruby-RRDtool ruby-augeas ruby-aws ruby-bsearch ruby-gnome2 ruby-icon-artist ruby-korundum ruby-ldap ruby-libvirt ruby-mecab ruby-ncurses ruby-qt ruby-rhubarb ruby-romkan ruby-shadow ruby-spqr ruby-taglib rubygem-RedCloth rubygem-RubyInline rubygem-atk rubygem-atomic rubygem-bcrypt-ruby rubygem-bson_ext rubygem-cairo rubygem-cairo-gobject rubygem-charlock_holmes rubygem-curb rubygem-eventmachine rubygem-fast_xs rubygem-ferret rubygem-ffi rubygem-gdk3 rubygem-gdk_pixbuf2 rubygem-gherkin rubygem-gio2 rubygem-glib2 rubygem-goocanvas rubygem-goocanvas1 rubygem-gstreamer rubygem-gtk2 rubygem-gtk3 rubygem-gtksourceview2 rubygem-hpricot rubygem-idn rubygem-json rubygem-kgio rubygem-krb5-auth rubygem-levenshtein rubygem-linecache19 rubygem-mechanize rubygem-mkrf rubygem-mysql2 rubygem-narray rubygem-newgem rubygem-nokogiri rubygem-opengl rubygem-pam rubygem-pango rubygem-parseconfig rubygem-passenger rubygem-pg rubygem-pkg-config rubygem-poppler rubygem-posix-spawn rubygem-qpid_messaging rubygem-qpid_proton rubygem-raindrops rubygem-rdiscount rubygem-redcarpet rubygem-rkerberos rubygem-rmail rubygem-rspec-longrun rubygem-rsvg2 rubygem-ruby-debug-base19 rubygem-ruby-libvirt rubygem-rufus-scheduler rubygem-rugged rubygem-sequel rubygem-snmp rubygem-sqlite3 rubygem-syck rubygem-therubyracer rubygem-thin rubygem-typhoeus rubygem-unf_ext rubygem-virt-p2v rubygem-vte rubygem-xmlhash rubygem-xmlparser rubygem-zoom rubygems saslwrapper shogun simspark skf sshmenu stfl subversion uwsgi vim vim-command-t wallaby weechat xapian-bindings xchat-ruby xmms2 zorba

2 1

Use rubygem(foo) or rubygem-foo
by Achilleas Pipinellis 07 Mar '14

07 Mar '14

I know that both result to the same thing (if I remember correctly I had asked Vit about this in IRC), but I have forgotten their real difference. My attention got caught by a comment Josef made in one of his reviews [0], saying that rubygem-foo is the new syntax. If that's the case, I would like to propose 2 changes: a) A reference in the wiki b) An implementation for gem2rpm I guess b) could be fairly easy by changing the templates. By starting with these steps, there will be a push to use the new syntax from now on. What do you think? [0]: https://bugzilla.redhat.com/show_bug.cgi?id=979749#c2 -- FAS : axilleas GPG : 0xABF99BE5 Blog: http://axilleas.me

4 11

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

ruby-sig March 2014