Why do Ruby libs still install in site_ruby?

[Bryan Duxbury]

We already have code in the Ruby libraries for packaging as a gem.  
Gems are clearly the preferred method of managing libraries in the  
Ruby world. So why does "make install" in the ruby lib put the bare  
library code in site_ruby? This strange arrangement makes it really,  
really easy to get yourself confused when developing on the ruby  
libs, since the site_ruby install takes precedence over any gem install.

Is anyone relying on this site_ruby installation behavior, or is it  
something we can just get rid of?

-Bryan