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...
11 years
gem-nice-install
by Vít Ondruch
Hi,
Today, I have released gem-nice-install RubyGems plugin, which helps you
to install binary gems on your Fedora/RHEL.
Any feedback welcome, as well as opinion, if we should integrate this
plugin on Fedora by default.
Vit
11 years
isitfedoraruby update
by Mo Morsi
Hey all, just pushed a few updates to the webapp and live site including:
- new feature pulling in all a gem / rpm's bugs from bugzilla and
highlighting the review bug on the rpm details page
- new feature pulling in builds from koji and highlighting them on the
rpm details page
- further analysis of rpm specfile to determine if upstream gem is
patched, this is done on a per fedora-version basis for each package
- more formatting fixes and view updates.
The updates are live at http://isitfedoraruby.com
-Mo
11 years, 1 month
rspec 2.11.x hits rawhide
by Mamoru TASAKA
Hello, ruby-sig folks:
I have just updated rspec rpms to 2.11.x on rawhide (F19)
rubygem-rspec-mocks-2.11.3-1.fc19
rubygem-rspec-core-2.11.1-1.fc19
rubygem-rspec-expectations-2.11.3-1.fc19
rubygem-rspec-2.11.0-1.fc19
Some notes:
* rubygem-rspec-core does not depend on -expectations and -mocks any
longer.
* rubygem-rspec-core no longer contains rspec.rb. If some package needs
"rspec.rb", replace (Build)Requires: rubygem(rspec-core) to rubygem(rspec).
I am not sure if we can push rspec 2.11.x also on F-18. F-18 beta
freeze has not come yet, so maybe it is still not late to push rspec
2.11.x also on F-18.
Regards,
Mamoru TASAKA <mtasaka(a)fedoraproject.org>
11 years, 1 month
JRuby 1.7.0 progress
by Bohuslav Kabrda
Hi folks,
I'm writing a quick summary of what I managed to achieve with JRuby/Fedora implementation so far. You can try out my repo at [1] and see the progress of work on jruby.spec at [2].
- I have managed to remove the RubyGems copy from JRuby and make them work with our system RubyGems - I had to apply few JRuby specific patches there - two are already accepted upstream, but not merged into the 1.8 tree, one is still pending [3]. The updated RubyGems are also in the mentioned repo and please be careful when installing them, preferably use mock.*
- As a part of the RubyGems modifications, I have also prepared a sample gem (rubygem-json, also in the repository), with a rubygem-json-java subpackage, that provides Java extensions for JRuby.
- Pure Gems from Fedora now work with JRuby out of the box, no modification needed.
- "jgem" command works exactly as "gem", only using JRuby - nice, isn't it? :)
- load paths set has been brought much closer to MRI, which allowed most of the stuff I have done
TODO:
- I'm still unsure what is the best way to set up the Provides/Requires, so that RubyGems would be installable without MRI, only with JRuby. I guess we can live with JRuby dragging in Ruby, that's a small problem for now :)
- Some modifications to Guidelines will be needed, explaining how to build Gems/non-Gems for JRuby.
- I will also add a jruby-devel package with macros.jruby to match MRI's behaviour closely.
* The reason for this is, that I have also tried to introduce new naming scheme for Gems extensions dirs, which is not compatible with the current one. So far, the %gem_extdir was "/usr/lib[64]/gems/exts". With Rubinius and JRuby comming, there is a slight problem - extensions for JRuby should of course go under /usr/share/gems/exts, but Rubinius extensions would have problems, as they should go under %gem_extdir, too. Therefore, I'd like to propose this scheme for extension placement:
%gem_extdir %{_libdir}/gems/ruby # MRI
%xgem_extdir %{_libdir}/gems/rubinius # Rubinius, not sure if that should be named "xgem_extdir", what do the others think?
%jgem_extdir %{_datadir}/gems/jruby #JRuby # JRuby
This logic to implement this is very simple and it all goes to defaults/operating_system.rb in the updated rubygems package in my repo (specfile is a bit adjusted, too).
There is also a question of versioning these dirs, mainly Rubinius exts, but I'm leaving that for future, comment if you have any good ideas :)
Thanks goes to Charles Nutter for taking the JRuby RubyGems close to upstream, which was very important from Fedora integration POV :)
Slavek.
--
Regards,
Bohuslav "Slavek" Kabrda.
[1] http://bkabrda.fedorapeople.org/jruby/jruby.repo
[2] https://github.com/bkabrda/jruby.spec
[3] https://github.com/rubygems/rubygems/pull/371
11 years, 2 months
gem-patch - a tool for patching gems
by Josef Stribny
Hi,
I want to let you know about gem-patch plugin that I made for both RubyGems 1.8.x and 2.0.x.
gem-patch is a RubyGems plugin that helps to patch gems without manually opening and rebuilding them.
It adds the `patch` command which opens a given .gem file, extracts it, patches it with system patch command,
clones its spec, updates the file list and builds the patched gem.
Intended as a new feature of RubyGems [1], it has been released as a gem [2], and source code (with separated branches
for RubyGems 1.8 and 2.0) is available on GitHub [3].
To use it:
- install the gem (0.1.1)
gem install gem-patch
- and patch:
gem patch GEMFILE PATCH [PATCH ...]
Regards
Josef
[1] https://github.com/rubygems/rubygems/pull/381
[2] https://rubygems.org/gems/gem-patch
[3] http://github.com/strzibny/gem-patch
11 years, 2 months
