trouble using RubyCocoa after Ruby update
Hey all, last week i did a ruby update using DP (should we say MP right now :-)) of Ruby, here is my setup : Mac OS X 10.4.8 ~%> ruby --version ruby 1.8.5 (2006-08-25) [powerpc-darwin8.8.0] ~%> gem --version 0.9.0 ~/Desktop/rb-appscript-0.1.5%> port --version MacPorts 1.320 after a successfull build of a WebKit/RubyCocoa app, then when launching it under XCode o got : opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such file to load -- rubycocoa (LoadError) from /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /opt/local/lib/ruby/vendor_ruby/1.8/osx/webkit.rb:14 from /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /Users/yvon/work/RubyCocoa/DOMTreeView/build/Release/DOMTreeView.app/Con tents/Resources/DOMDataSource.rb:12 from /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' from /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /Users/yvon/work/RubyCocoa/DOMTreeView/build/Release/DOMTreeView.app/Con tents/Resources/rb_main.rb:18:in `rb_main_init' from /Users/yvon/work/RubyCocoa/DOMTreeView/build/Release/DOMTreeView.app/Con tents/Resources/rb_main.rb:17:in `each' from /Users/yvon/work/RubyCocoa/DOMTreeView/build/Release/DOMTreeView.app/Con tents/Resources/rb_main.rb:17:in `rb_main_init' from /Users/yvon/work/RubyCocoa/DOMTreeView/build/Release/DOMTreeView.app/Con tents/Resources/rb_main.rb:23 the apps i want to test on my box are from "RubyCocoa Resources" <http://www.rubycocoa.com/rubification-central/1#page1> projects named "DOMTreeView" and "Downloader" another project failed to run, under command line found in "Cocoa Magic for Gruff Graphs" <http://www.rubycocoa.com/cocoa-magic-for-gruff-graphs> here is the trial : ~/Desktop/gruff-0.2.4%> ruby /Users/yvon/Desktop/gruff-0.2.4/test/test_line.rb opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require': no such file to load -- rubycocoa (LoadError) from /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /opt/local/lib/ruby/vendor_ruby/1.8/osx/cocoa.rb:11 from /opt/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require' those probs arroses only apfet DP/MP update of ruby. may be this is as simple as moving a folder to another one, because the old install of rubycocoa/rubygems are lying under the old version of ruby, may be a good solution to cure that would be to re-inctall both rubycocoa and rubygems under the new ruby installed by MP|DP ??? in which case i'd like to know how to clean up DP|MP xithin my box because for example i have : %> port installed apache2 @2.2.0_0 apache2 @2.2.2_1 apache2 @2.2.3_0 (active) i think it is at leasst unusefull the let the apache2 old versions on my box rather more or les "dangerous". then how to uninstall an old versio after a successfull install of a new one ? Yvon
Citando Yvon Thoraval :
Hey all, [...]
in which case i'd like to know how to clean up DP|MP xithin my box because for example i have :
%> port installed apache2 @2.2.0_0 apache2 @2.2.2_1 apache2 @2.2.3_0 (active)
i think it is at leasst unusefull the let the apache2 old versions on my box rather more or les "dangerous".
then how to uninstall an old versio after a successfull install of a new one ?
It is not dangerous, it only means you have three versions built on your system, but the only one that can work is the one active, lying in ${prefix} (the other (in fact, all installed versions, the active version only makes links to this place) are kept in ${prefix}/var/db/dports/software/) that way you can roll back to an older version if the new one does not work well. However, it takes space on your hard drive. To uninstall one version, just use "uninstall", for example sudo port uninstall apache2 @2.2.0_0 To do a rollback, you have to deactivate the active version then activate the older one, for example: sudo port deactivate apache2 @2.2.3_0 sudo port activate apache2 @2.2.2_1 (I do not know about your ruby problems...) Emmanuel
Le 21 oct. 06 à 10:25, Emmanuel Hainry a écrit :
It is not dangerous, it only means you have three versions built on your system, but the only one that can work is the one active, lying in ${prefix} (the other (in fact, all installed versions, the active version only makes links to this place) are kept in ${prefix}/var/db/dports/software/) that way you can roll back to an older version if the new one does not work well. However, it takes space on your hard drive.
To uninstall one version, just use "uninstall", for example sudo port uninstall apache2 @2.2.0_0
To do a rollback, you have to deactivate the active version then activate the older one, for example:
sudo port deactivate apache2 @2.2.3_0 sudo port activate apache2 @2.2.2_1
ok, fine thanks, i'l wait for uninstalling oldest the newest are working weel.
(I do not know about your ruby problems...)
ok i'll wait also for an advice on that topic )) in between i'll install what i need into my HOME ))) best, Yvon
participants (2)
-
Emmanuel Hainry
-
Yvon Thoraval