Sorry, my answer was partly wrong: “igem install” will still install into redist_libs/ironruby/gems. Gems will be loadable from IronRuby if they are in both locations, so it shouldn’t stop stuff from working. If you don’t like this behavior, and want all your IronRuby gems in one place, the either unset GEM_PATH or set GEM_HOME to be the same as GEM_PATH, depending on where you want gems to be installed and loaded from.
I think setting GEM_PATH to point at ruby-1.8.6p287 only helps people who have a Microsoft TFS enlistment to the IronRuby sources, as there is a full MRI installation at Merlin\External.LCA_RESTRICTED\Languages\Ruby\ruby-1.8.6p287. If that’s the case, then we should fix this. Anyone else have insight into why we have two copies of the libraries checked in, and gems are split up between them? From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Riley Sent: Wednesday, August 05, 2009 9:51 PM To: [email protected] Subject: Re: [Ironruby-core] Dev.bat and GEM_PATH Install gems using the gem command? igem seems to install into the ..\redist_libs\ironruby folder. At least, I think that's where they are going. Just trying to make sure I understand what's happening. Thanks! R2 On Wed, Aug 5, 2009 at 11:44 PM, Jimmy Schementi <[email protected]<mailto:[email protected]>> wrote: It uses ruby-1.8.6p287 so we can install gems, and even check them in, but not compromise the integrity of anything under redist_libs: it’s the cleanroom copy of the Ruby libraries. If you diff them your only see these changes: certain words filtered out that Microsoft does not allow in source code, bugs in the standard libs (using + instead of ^ with hashes) and certain library files removed that IronRuby won’t support (eg. Tk).
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
