From: Eric Hodel <drbrain@...7.net>
Date: 2005-11-18T03:53:16+09:00
Subject: Re: gem and stubs

On Nov 16, 2005, at 7:42 PM, Gavin Sinclair wrote:

> Ara.T.Howard wrote:
>> what's the deal?  does it support them or not?  the docs are  
>> confusing on the
>> matter, but the latest certainly does not support them by default  
>> and also no
>> longer accepts the --install-stubs option.
>
> Library stubs have been unsupported for ages.  In fact, when you
> install RubyGems, it looks for any existing library stubs and removes
> them :)
>
> When "require" gained the ability to look for libraries in installed
> gems, library stubs were no longer needed or wanted.
>
> Application stubs are a different matter.  If a gem includes any
> executables, they are proxied in your "bin" directory whether you like
> it or not.  AFAIK, there's no option to control that.

$ gem install --help
   Options:
     -v, --version VERSION            Specify version of gem to install
     -l, --local                      Restrict operations to the  
LOCAL domain (default)
     -r, --remote                     Restrict operations to the  
REMOTE domain
     -b, --both                       Allow LOCAL and REMOTE operations
     -i, --install-dir DIR
     -d, --[no-]rdoc                  Generate RDoc documentation for  
the gem on install
     -f, --[no-]force                 Force gem to install, bypassing  
dependency checks
     -t, --[no-]test                  Run unit tests prior to  
installation
     -w, --[no-]wrappers              Use bin wrappers for executables
                                      Not available on dosish platforms
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Courtesy the Seattle.rb Rubygems Hackfest

-- 
Eric Hodel - drbrain@segment7.net - http://segment7.net
FEC2 57F1 D465 EB15 5D6E  7C11 332A 551C 796C 9F04