On 06/18/2010 03:48 PM, Mamoru Tasaka wrote:
Hello, Mohammed
Mohammed Morsi wrote, at 06/19/2010 02:03 AM +9:00:
Sorry, it doesn't seem like my original response made it through (at least not according to the ruby-sig archive http://lists.fedoraproject.org/pipermail/ruby-sig/2010-June/thread.html). Resending.
-Mo
-------- Original Message -------- Subject: Re: ruby 1.8.7.x for rawhide Date: Fri, 18 Jun 2010 12:44:56 -0400 From: Mohammed Morsimmorsi@redhat.com To: Ruby SIG mailing listruby-sig@lists.fedoraproject.org CC: Mamoru Tasakamtasaka@ioa.s.u-tokyo.ac.jp, ruby-owner@fedoraproject.org
Hey Mamoru,
Appreciate the efforts. I am also working towards Ruby 1.8.7 onFedora, just released a SRPM/SPEC a few days ago that I was working on
http://mo.morsi.org/blog/node/318Thank you for your another work for ruby 1.8.7. Hopely we can merge our efforts altogether and import ruby187 to (at least) rawhide soon.
By the way I just looked at your srpm (on your blog) quickly and also tried binary rpms rebuilt your srpm quickly. I thinking defining %ruby_sitearch or so is preferred because we already use such macros in ruby related srpms. For rawhide I think we should create /etc/rpm/macros.ruby18 . However, with ruby rpms rebuilt from your srpm, ruby returns:
I readded the macros you mentioned to my specfile.
mock-chroot> ruby -v ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-linux] mock-chroot> ruby -e 'puts $:'
/usr/lib/ruby//site_ruby /usr/lib/ruby//site_ruby /usr/lib/ruby//site_ruby
Sorry for the delay, uploaded a new SRPM with these path issues fixed. All the directories currently present on the path are now there again, as well a bunch of new '1.8.7' subdirs in preperation for the parallel installable ruby stacks. The new srpm can be found here:
http://mo.morsi.org/files/ruby-1.8.7.249-2.fc13.src.rpm
. mock-chroot> ruby -rrbconfig -e 'puts Config::CONFIG["sitearchdir"]' ruby: no such file to load -- rbconfig (LoadError)
On the other hand, from rpms rebuilt from my srpm:
mock-chroot> ruby -v ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-linux] mock-chroot> ruby -e 'puts $:' /usr/lib/ruby/site_ruby/1.8 /usr/lib/ruby/site_ruby/1.8/i386-linux /usr/lib/ruby/site_ruby /usr/lib/site_ruby/1.8 /usr/lib/site_ruby/1.8/i386-linux /usr/lib/site_ruby /usr/lib/ruby/vendor_ruby/1.8 /usr/lib/ruby/vendor_ruby/1.8/i386-linux /usr/lib/ruby/vendor_ruby /usr/lib/ruby/1.8 /usr/lib/ruby/1.8/i386-linux
Running this on a 64 bit F13 install, also yields the following dirs
/usr/lib64/site_ruby/1.8 /usr/lib64/site_ruby/1.8/x86_64-linux /usr/lib64/site_ruby
The only thing is the /usr/lib64/site_ruby dir doesn't exist (the ruby package in Fedora doesn't provide it apparently, unless I'm mistaken), so I omitted these entries. If this is a mistake, they can be readded easily and the rpm spec changed to generate that dir.
. mock-chroot> ruby -rrbconfig -e 'puts Config::CONFIG["sitearchdir"]' /usr/lib/ruby/site_ruby/1.8/i386-linux
Also, currently we usually define %ruby_sitearch as $(ruby -rrbconfig -e 'puts Config::CONFIG["sitearchdir"]'), which currently returns as above (i.e. /usr/lib/ruby/site_ruby/1.8/i386-linux), and I think we shouldn't change these paths with the update from 1.8.6.x to 1.8.7.x (when importing 1.9.x ruby in parallel, I think we can consider to change these paths in ruby 1.9).
This was due to the missing lib paths, now rbconfig loads fine.
Just fyi, we're also going to need this patch
http://redmine.ruby-lang.org/repositories/diff/ruby-187?rev=27408To get rails 3.0.0 working against Ruby 1.8.7p149
http://redmine.ruby-lang.org/issues/show/2557Well, I just git-cloned rails.git and it seems that unicode_database.rb can no longer be found in rails tree. Instead I found unicode_database.rb in activesupport 2.3.5 but it won't cause crash even with my 1.8.7.249 srpm - maybe because I use "-fno-strict-aliasing". However anyway I applied this patch and it can be found on:
http://koji.fedoraproject.org/scratch/mtasaka/task_2258338/ (currently only rebuilt for rawhide, however srpm can also be found here)
I added this patch to my specfile as well, bumped the release, and updated the changelog to include your feedback.
-Mo