=begin
I noticed a strange behaviour while testing my libraries with Ruby 1.9.1-p0. I successfully installed ronin version 0.2.2 and ronin-scanners version 0.1.3 with Ruby 1.9.1-p0. When I attempted to load the ronin RubyGem using "gem 'ronin'", I noticed that ronin-scanners 0.1.3 was also loaded into $LOAD_PATH. Since lib/ directories with similar layouts were included into the $LOAD_PATH, this caused various loading issues.
Note: ronin-scanners version 0.1.3 depends on ronin >= 0.2.1, but ronin-scanners is not required by ronin and should not need to be loaded by RubyGems. This behaviour could not be reproduced with Ruby 1.8.6, so I'm left to believe this is a Ruby 1.9.x specific issue.
=end
I noticed a strange behaviour while testing my libraries with Ruby
1.9.1-p0. I successfully installed ronin version 0.2.2 and ronin-
scanners version 0.1.3 with Ruby 1.9.1-p0. When I attempted to load
the ronin RubyGem using "gem 'ronin'", I noticed that ronin-scanners
0.1.3 was also loaded into $LOAD_PATH. Since lib/ directories with
similar layouts were included into the $LOAD_PATH, this caused
various loading issues.
If I understand you correctly, it isn't the gem command, it is ruby
1.9 in general. Look at your $: before calling #gem at all. This is
intentional behavior.
Updated by 
Updated by 
Updated by