From: Rimantas Liubertas <rimantas@...>
Date: 2007-01-27T08:43:02+09:00
Subject: Re: RubyGems 0.9.1 calling a gem with gem '<gem>'

> I was using: gem 'uuid'
>
> because I had been using: require_gem 'uuid'
> but ran in to the deprecated warning that many people have already
> discussed:
>
> Warning: require_gem is obsolete.  Use gem instead.
>
> Maybe I'm misinterpreting the "Use gem instead" part?

It depends :) 'gem' tells your program that you are going to use some
gem, but it does not
require it, so you still have to use 'require'.
Let's say you have two versions of 'my_gem', 0.1 and 0.2. rubygems
will use the latest by default, but in case you need the first version
you can do the following:

require 'rubygems'
gem 'my_gem', '=0.1'
require 'my_gem'

I think you've got bitten by the autorequire feature wich no longer
works. require_gem used to specify the gem and require it, 'gem' only
add the gem to load path, you still have to require it.


-- 
Regards,
Rimantas
--
http://rimantas.com/