Matt Jones wrote: > Take a careful look at the errtheblog article - you should be using > require, not gem here. > The gem statements only add the gem directories to the load_path.
Changing to 'require' got past that error. I still don't understand why it failed to load since I had requires elsewhere that just didn't specify the version. Where would I look up the syntax reference for 'gem' and 'require' ? I'm not really clear where those come from. I see 'require' documented here: http://www.rubygems.org/read/chapter/3 but it doesn't reference the version argument and I don't see where 'gem' is documented. > In the long run, you should definitely switch over to using > config.gem, but that isn't an > option with Rails 2.0.3. I'll give that a look when we upgrade. > BTW, even changing to 'require's is still going to leave you with > problems, as RMagick's > native component hasn't been built yet. I don't know of any easy way > to do it in your > situation. Thanks for the warning. > You might want, for the short term, to just leave the 'gem' > lines in your environment > and keep the gem packages for the gems you need around. That way, the > code will complain > loudly if the gems needed aren't installed. Hmmm... so it seems that 'gem' just declares that the code depends on a gem, and 'require' actually loads the library? Thanks so much! Sarah -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
