On Nov 30, 2006, at 0805 , Chad Fowler wrote: > On 11/30/06, Thibaut Barrère <[EMAIL PROTECTED]> wrote: >> I'm working with some ruby scripts stored under subversion. Some >> of those >> scripts requires gems (like the builder gem for instance, or >> activerecord). >> I'd like to avoid to have to run 'gem install builder' on each >> developer >> machine, in order to rely solely on what is in subversion. >> >> For that purpose I've unpacked the required gems in a version- >> controlled >> folder. >> >> Is there a preferred way of telling the gems loader to include all >> the >> unpacked gems available in this folder ? (while keeping the "require >> 'builder'" statement working ?) > > Now that you've unpacked the gem, using it is no longer a gem-specific > task. You just need to add each gem's lib directory (or equivalent) > to Ruby's load path. What I would do is to loop through the directory > in which you unpacked each gem, and unshift that directory's lib > subdirectory onto the $: object (somewhere before you try to use the > library).
Also, you can set the RUBYLIB environment variable. -- Eric Hodel - [EMAIL PROTECTED] - http://blog.segment7.net I LIT YOUR GEM ON FIRE! _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
