transfire wrote:
> Wait a minute! That doesn't work.
> 
> Jim, if I tell it to inlcude 'packages/**/lib/**/*' then it includes
> them but just like that in the gem. It makes no sense. Wouldn't one
> then have to use?
> 
>   require 'packages/proj1/lib/proj1/file.rb'
> 
> Even using require_paths isn't helpful b/c I have dozens of
> sub-projects. Considering how Gems works I'm pretty sure  that would
> way too inefficent.
> 
> Is there are way to tell it how to put them in the gem?

You tell the gem spec where your library directories are (the default is 
just "lib").  RubyGems will make sure they all get added to the load 
path at run time.

-- Jim Weirich


-- 
Posted via http://www.ruby-forum.com/.