Search path order, probably. Julian.
On 22/09/2008, at 1:13 PM, Scott M. Likens wrote: > Julian, > > That's the catch 22. > > You symlink them, and you are stuck using the systems path for ruby > instead of the proper path. Now if you symlink everything that's > great, fantastic and it works. > > However, as you may know 10.5.5 combo updater .. .updated rake and > rubygems to 1.2.0 and stuck them in /usr/bin.... it didn't put in > ruby (yes I rm'd them, and have 0 issues) so when I did gem install > merb, it stuck them in the /Library instead of /usr/local prefix > and ... showed a glaring prefix issue with rubygems. > > Ruby scripts that are installed in /usr/bin (e.g. /usr/bin/merb) > will look in /Library/Ruby/Gems/1.8/gems instead of looking in /usr/ > local/lib/ruby/1.8/gems/1.8/gems > > don't ask me why/how/etc... i've just had it happen. > > Julian Leviston wrote: >> >> Yes, but if he does this, certain scripts which are accessing the >> previous version will break. >> >> better to symlink these old files to the new ones, I reckon... maybe >> not though :) >> >> Julian. >> >> On 22/09/2008, at 12:57 PM, Scott M. Likens wrote: >> >> >>> Peter, >>> >>> Looks like you have an old version of ruby dangling around >>> somewhere, >>> more then likely in /usr/bin/ruby and you modified your path to >>> include >>> /usr/local/bin or wherever you installed the later version of ruby >>> at? >>> >>> Ruby 1.8.2 came with Tiger, and it looks like one of those is >>> running >>> Tiger ... it's the annoyance of having ruby on OS X, if you don't >>> use >>> the System Ruby you have to remove it, and then install it in >>> /usr/local/bin and then ensure any "ruby" scripts are not >>> installed in >>> /usr/bin as they will try to use the systems gempath instead of the >>> new >>> gempath for ruby. >>> >>> The Bottom line is, you have ruby 1.8.2 on one of those machines, >>> and >>> you need to remove it. >>> >>> sudo rm /usr/bin/ruby /usr/bin/irb /usr/bin/rake >>> >>> hash -r >>> >>> then try. >>> >>> >>> Peter wrote: >>> >>>> Hi, >>>> >>>> Anybody seems this before when running bin/merb? >>>> >>>> http://pastie.org/276942 >>>> >>>> I used thor and installed all merb gems into gems folder. List: >>>> >>>> ParseTree-2.2.0 >>>> RubyInline-3.7.0 >>>> abstract-1.0.0 >>>> builder-2.1.2 >>>> cgi_multipart_eof_fix-2.5.0 >>>> daemons-1.0.10 >>>> data_objects-0.9.6 >>>> diff-lcs-1.1.2 >>>> english-0.2.0 >>>> erubis-2.6.2 >>>> extlib-0.9.7 >>>> facets-2.4.4 >>>> fastthread-1.0.1 >>>> gem_plugin-0.2.3 >>>> haml-2.0.3 >>>> highline-1.4.0 >>>> hoe-1.7.0 >>>> hpricot-0.6.161 >>>> json_pure-1.1.3 >>>> mailfactory-1.4.0 >>>> merb-action-args-0.9.8 >>>> merb-assets-0.9.8 >>>> merb-auth-0.1.0 >>>> merb-builder-0.9.8 >>>> merb-cache-0.9.8 >>>> merb-core-0.9.8 >>>> merb-gen-0.9.8 >>>> merb-haml-0.9.8 >>>> merb-jquery-0.9.8 >>>> merb-mailer-0.9.8 >>>> merb-more-0.9.8 >>>> merb-parts-0.9.8 >>>> merb-slices-0.9.8 >>>> merb_datamapper-0.9.8 >>>> merb_has_flash-0.9.6 >>>> merb_helpers-0.9.8 >>>> mime-types-1.15 >>>> mongrel-1.1.5 >>>> rack-0.4.0 >>>> rake-0.8.1 >>>> rspec-1.1.4 >>>> ruby2ruby-1.1.9 >>>> rubyforge-1.0.0 >>>> templater-0.2 >>>> thor-0.9.6 >>>> >>>> and I have datamappers gems in the system. >>>> >>>> Weird is I don't have Ruby 1.8.2, I have ruby -v >>>> ruby 1.8.6 (2008-03-03 patchlevel 114) [i686-darwin8.11.1] >>>> >>>> I have this same thing working in another Intel/Mac: >>>> ruby 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0] >>>> >>>> Thanks, >>>> >>>> Peter. >>>> >>>> >>>> >>>> >>>> >>>> >>> >> >> >> >> !DSPAM:48d70a9a250987214431416! >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
