Created attachment 391348 [details] simple ruby script showing the effects of this bug qtruby-4.14.3-r1 uses ruby 2.0, but according to KDE bug 330800, it doesn't work correctly because signals defined in ruby programs aren't emitted. Since defining signals in ruby is quite common, this bug makes qtruby unusable with ruby 2. The bug report also includes a patch which should make qtruby work with ruby 2. I attach a simple ruby file which shows this behaviour. When run using qtruby-4.14.3 and ruby 1.9.3, it prints the text "SIGNAL RECEIVED". When run using qtruby-4.14.3-r1 with ruby 2.0, it prints nothing. When applying the patch mentioned in the KDE bug report, it works correctly again. Note that, while the patch works for this simple script, I've not tested it in real programs so, while it should fix this problem, I'm not sure whether it has other, unintended consequences.
Created attachment 391350 [details, diff] patch to fix this bug This is the patch suggested in the KDE bug report to fix this bug
Thanks for reporting. This is fixed in cvs now please sync in some hours to get the changes. + + 18 Jan 2015; Johannes Huber <johu@gentoo.org> + +files/qtruby-4.14.3-ruby20.patch, +qtruby-4.14.3-r2.ebuild, + qtruby-4.14.3.ebuild: + Revision bump adds patch to fix signals in ruby20 spotted by Stefano Crocco + <stefano.crocco@alice.it>, bug #532120. +
