Hello, all:
I have updated rubygems to 1.5.0. If you see some issues with new rubygems,
please feel free to file bugs.
Some notes I have noticed for now:
- Some gem based packages install ruby wrapper scripts under /usr/bin which contain
something like
-----------------------------------------------------------------
#!/usr/bin/ruby
# This file was generated by RubyGems.
require 'rubygems'
version = ">= 0"
if ARGV.first =~ /^_(.*)_$/ and Gem::Version.correct? $1 then
version = $1
ARGV.shift
end
gem 'foo', version
load 'foo'
-----------------------------------------------------------------
The last line "load 'foo'" style is now obsolete and rubygems 1.5.0 will
no longer accept this. For example, /usr/bin/rake in rubygem-rake-0.8.7-2.fc12.noarch
will no longer work like:
-----------------------------------------------------------------
$ /usr/bin/rake
/usr/bin/rake:19:in `load': no such file to load -- rake (LoadError)
from /usr/bin/rake:19
-----------------------------------------------------------------
The pkgs containing scripts under /usr/bin with this old style needs rebuilding.
Note that
- currently mass rebuild for F-15 is in progress, and once rebuilt pkgs are
tagged into dist-f15, this will no longer be the issue.
- also for rubygem-rake, newly rebuilt rubygem-rake-0.8.7-4.fc15 is already in dist-f15
buildroot, so on dist-f15 buildroot $ rake test or so should not fail with
this change.
- Some gem based pkgs generate .required_paths under %geminstdir. With rubygems
1.5.0 this file does not seem to be generated, so if spec file contains
.reqired_paths build may fail.
Happy hacking!
Regards,
Mamoru