class Gem::Commands::InstallCommand

def description # :nodoc:
  <<-EOF
e install command installs local or remote gem into a gem repository.
r gems with executables ruby installs a wrapper file into the executable
rectory by default.  This can be overridden with the --no-wrappers option.
e wrapper allows you to choose among alternate gem versions using _version_.
r example `rake _0.7.3_ --version` will run rake version 0.7.3 if a newer
rsion is also installed.
m Dependency Files
==================
byGems can install a consistent set of gems across multiple environments
ing `gem install -g` when a gem dependencies file (gem.deps.rb, Gemfile or
olate) is present.  If no explicit file is given RubyGems attempts to find
e in the current directory.
en the RUBYGEMS_GEMDEPS environment variable is set to a gem dependencies
le the gems from that file will be activated at startup time.  Set it to a
ecific filename or to "-" to have RubyGems automatically discover the gem
pendencies file by walking up from the current directory.
TE: Enabling automatic discovery on multiuser systems can lead to
ecution of arbitrary code when used from directories outside your control.
tension Install Failures
========================
 an extension fails to compile during gem installation the gem
ecification is not written out, but the gem remains unpacked in the
pository.  You may need to specify the path to the library's headers and
braries to continue.  You can do this by adding a -- between RubyGems'
tions and the extension's build options:
$ gem install some_extension_gem
[build fails]
Gem files will remain installed in \\
/path/to/gems/some_extension_gem-1.0 for inspection.
Results logged to /path/to/gems/some_extension_gem-1.0/gem_make.out
$ gem install some_extension_gem -- --with-extension-lib=/path/to/lib
[build succeeds]
$ gem list some_extension_gem
*** LOCAL GEMS ***
some_extension_gem (1.0)
$
 you correct the compilation errors by editing the gem files you will need
 write the specification by hand.  For example:
$ gem install some_extension_gem
[build fails]
Gem files will remain installed in \\
/path/to/gems/some_extension_gem-1.0 for inspection.
Results logged to /path/to/gems/some_extension_gem-1.0/gem_make.out
$ [cd /path/to/gems/some_extension_gem-1.0]
$ [edit files or what-have-you and run make]
$ gem spec ../../cache/some_extension_gem-1.0.gem --ruby > \\
           ../../specifications/some_extension_gem-1.0.gemspec
$ gem list some_extension_gem
*** LOCAL GEMS ***
some_extension_gem (1.0)
$
mmand Alias
========================
u can use `i` command instead of `install`.
$ gem i GEMNAME
  EOF
end