Ruby and Fedora 17
by Bohuslav Kabrda
Hi all,
since Ruby/Fedora integration had some significant changes from F16 to F17, I thought it might be a good idea to write a summary of new features and send it out for all - see [1].
All comments and suggestions for further development are welcome.
--
Regards,
Bohuslav "Slavek" Kabrda.
[1] http://bkabrda.fedorapeople.org/fedora17-ruby-eng-v2.pdf
11 years, 9 months
ABRT for Ruby
by Vít Ondruch
Hello,
I've put together some basic implementation of ABRT support for Ruby. It
means that whenever your application/library fails in Ruby code (note
that this does not catch segfaults), it will be easy to your users to
report such problem into Bugzilla.
Source code: https://github.com/voxik/abrt-ruby
Gem: gem install abrt
ATM, there are several ways how to test the gem:
1) "require 'abrt'" in your code, as soon as possible, but later then
rubygems if you are using Ruby 1.8.
2) If you are already using Ruby 1.9, you can add "RUBYOPT='-rabrt'"
into your environment. This assures that every time Ruby is started, the
abrt gem is activated. Unfortunately, this doesn't work with Ruby 1.8,
since RubyGems are not loaded by default and "RUBYOPT='-rubygems
-rabrt'" does not work for some reason :/
Please note that ABRT reports errors just for Ruby libraries managed by
RPM. If something appears to not work as expected, it is good to observe
/var/log/messages for more details.
In the future, I'd love to see this integrated into Ruby (probably in
F18?). I already asked upstream about possible integration [1], but if
went without response, so it seems that I will have to come with some
proposal.
I'd love to here your comments and of course your patches :)
Thank you
Vit
[1] http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/42236
11 years, 10 months
Status on a BZ? (830234)
by Darryl L. Pierce
https://bugzilla.redhat.com/show_bug.cgi?id=830234
This bug is a blocker for my main upstream project (Qpid, and also our
upcoming Proton codebase). It's also blocking our ability to move from
automake tools to Cmake for our packaging as well. The problem is
consistently:
Scanning dependencies of target cqpid_ruby
[ 89%] Building CXX object
bindings/qpid/ruby/CMakeFiles/cqpid_ruby.dir/rubyRUBY_wrap.o
In file included from /usr/include/ruby.h:32:0,
from
/home/mcpierce/temp/cmake/bindings/qpid/ruby/rubyRUBY_wrap.cxx:856:
/usr/include/ruby/ruby.h:24:25: fatal error: ruby/config.h: No such file or directory
compilation terminated.
make[2]: *** [bindings/qpid/ruby/CMakeFiles/cqpid_ruby.dir/rubyRUBY_wrap.o] Error 1
make[1]: *** [bindings/qpid/ruby/CMakeFiles/cqpid_ruby.dir/all] Error 2
make: *** [all] Error 2
The package config file does not tell the configuration tool about
/usr/include/x86_64-linux, which holds the headers in question.
Is anybody working on this problem? And does anybody have a temporary
workaround for Cmake environments?
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
11 years, 10 months
