Ruby 2.0
by Vít Ondruch
Hi,
Just for your information, I have pushed ruby-2.0 branch into the Ruby's
git repo. So if you like test the latest Ruby, you need to get the
latest HEAD tarball, which could be prepared using:
$ cd /path/to/your/ruby/sources
$ ./tool/make-snapshot tmp
Note that you have to have available subversion and bison on your
system. Also note that the content of tarball is needed to be repacked,
that the Ruby sources will be stored in "ruby-2.0.0-p0" folder (I know,
it is annoyance, but you can fix the spec and send me a patch ;). Also
note that I currently keep the ruby_abi at 1.9.1, while the official
release will have 2.0.0 probably. This should allow you to use Fedora's
gems without rebuild. Any comments/patches are appreciated.
Vit
[1]
http://pkgs.fedoraproject.org/gitweb/?p=ruby.git;a=tree;h=refs/heads/ruby...
10 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, 2 months
Gemfile.lock questions
by Ken Dreyer
I have two more Ruby newbie questions :)
I see a lot of Gems contain a "Gemfile.lock" file. From looking at the
conventions in Fedora's packages, it's a good idea to not include the
Gemfile.lock in RPMs. I'm trying to understand how Gemfile.lock
relates to packaging.
General question: Is Gemfile.lock only intended to be a convenience
for Ruby Gem developers? I thought Gemfile.lock was only for
development, but it seems like its contents can also affect an
application's runtime...?
Packaging question: In preparation for packaging up Gitorious, I've
found that I need to delete some entries from Gemfile.lock in order to
use alternate Gem versions. Is it always safe to override the version
numbers in Gemfile.lock like this?
- Ken
11 years, 3 months
packaging gem tests
by Ken Dreyer
I'm wondering about how to handle things like the Rakefile, or /spec,
or /test directories in rubygem packages. My inclination is to leave
these out of the package to keep it slimmer, but I see that some
rubygems do include them in the package (or at least the -doc
subpackage). The example on the Ruby packaging guidelines also
includes these in -doc.
Are these files really that useful to ship to end users?
- Ken
11 years, 5 months
Ruby / Fedora GSoC
by Mo Morsi
Hey all I wanted to introduce and congratulate Zuhao who'se project
proposal [1] to expand the tooling around Fedora / Ruby integration as
well as the community promotional effort was accepted as part of the
Google Summer of Code!
I'm starting to working with Zuhao to implement the strategies he
outlined in his proposal. We're going to start by setting up a repo on
github w/ the basic rails project layout and starting to add features
from there. We aim to keep the process very rapid and agile, adding
things as needed until we have a solid feature set flushed out and ready
to deploy.
We'll figure out the hosting and domain requirements from there, if need
be I'll just register the domain myself and we can host it on
fedorapeople or one of my personal hosting solutions until we have
something more permanent (I have a linode and hostmonster accounts which
we can leverage for this as well as my own personal server running at home).
I'd also like to keep the process as open to the ruby-sig as possible.
Going forward if you have any more suggestions (including an alternative
name, isitfedoraruby could be improved upon) or would like to contribute
features / patches that you would like to see implemented yourself, by
all means shout out here or via IRC.
Should be a great summer of ruby! :-)
-Mo
[1]
https://fedoraproject.org/wiki/GSOC_2012/Student_Application_Zuhao/IsItFe...
11 years, 5 months
Re: [GSoC] What would you like to see in IsItFedoraRuby.com?
by Jeroen van Meeuwen
On 2012-04-10 12:09, Mo Morsi wrote:
> On 04/09/2012 06:07 PM, Zuhao wrote:
>> Hi Everyone,
>>
>> IsItFedoraRuby.com is an idea proposed in this year's Google Summer
>> of
>> Code. The website will be mainly used for tracking the progress of
>> the
>> conversion of each gem (similar to isitruby19.com
>> <http://isitruby19.com>), promoting the Fedora/Ruby integration, as
>> well as highlighting some success stories. Hopefully, this website
>> will let more people to be aware of the project, and thus more would
>> contribute to make it better.
>>
>> I have drafted a proposal with some preliminary design of the
>> website.
>> I would love to hear any thoughts or suggestions from you. As a
>> developer, what do you want to see on this website so that it can be
>> most helpful to the Fedora/Ruby community?
>>
>> The proposal is at:
>>
>> https://fedoraproject.org/wiki/GSOC_2012/Student_Application_Zuhao/IsItFe...
>>
>> Any feedback is much appreciated!
>>
>> Thanks,
>>
>> Zuhao
>>
>
> Hey Zuhao, thanks for the submission. the proposal looks very strong,
> and the mockups look great.
>
> I encourage anyone else who may have any additional ideas as how to
> promote Ruby on Fedora and/or develop additional tooling to
> streamline
> the Ruby to Fedora process to respond here and/or on the proposal
> itself.
I've often had questions (after the usual question of what gem version
is in what version of what platform (between Fedora/EPEL/RHEL)) about
whether a specific version of a gem distributed with a given version of
the platform had;
1) been updated with CVE patches,
2) been patched to negate bugs.
Depending on the feasibility, of course, perhaps there's opportunity to
contain that information in isitfedoraruby.com as well?
Kind regards,
Jeroen van Meeuwen
--
Systems Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com
pgp: 9342 BF08
11 years, 5 months
Updating cucumber
by Bohuslav Kabrda
Hi guys,
I would like to ask anyone of you, who has the ACLs to rubygem-cucumber, to update it to the latest upstream. I need it for a new gem aruba, which we need to run tests for rubygem-factory_girl_rails. I have filled a bugzilla on this [1], but Jeroen is not responding and I saw that there is plenty of you having the ACLs, so could someone please do it? :)
Thanks a lot.
--
Regards,
Bohuslav "Slavek" Kabrda.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=797206
11 years, 5 months
hardcoding API numbers
by Ken Dreyer
Hi all,
I'm a newbie to Ruby and Gems packaging, and I was wondering about a
convention I see in the rubygem packages. I see Ruby Gems hardcode
specific version numbers, like "ruby(api) = 1.8", or "ruby(api) =
1.9.3"? In Perl modules we specify it like this:
Requires: perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo $version))
so all Perl modules will Require: whatever Perl version was in the
buildroot. This makes it easy to use the same spec throughout multiple
distros (rawhide through EL5), even when the Perl versions on each OS
happen to be different. I was wondering why Ruby's Gems would hardcode
the Ruby version number?
- Ken
11 years, 5 months
