To build a certificate for signing gems: The cleanup command removes old versions of gems from GEM_HOME that are not required to meet a dependency.If a gem is installed elsewhere in GEM_PATH the cleanup command won’t delete it.The given directory will be the directory you serve as the gem repository.For The extension files are compressed with the inflate algorithm.false, true, and :really are the levels :update_sources: Enable/disable automatic updating of repository metadata :backtrace: Print backtrace when Ruby Gems encounters an error :gempath: The paths in which to look for gems :disable_default_gem_server: Force specification of gem server host on push Ruby Gems’ default local repository can be overridden with the GEM_PATH and GEM_HOME environment variables.GEM_HOME sets the default repository to install into.For local gems only the reverse dependencies can be shown (which gems depend on the named gem).
When the RUBYGEMS_GEMDEPS environment variable is set to a gem dependencies file the gems from that file will be activated at startup time.
You may override these in lib/rubygems/defaults/operating_Download a gem and place it in the current directory The fetch command fetches gem files that can be stored for later use or unpacked to examine their contents.
See the build command help for an example of unpacking a gem, modifying it, then repackaging it.
Command line argument defaults and some Ruby Gems defaults can be set in a ~/.gemrc file for individual users and a gemrc in the SYSTEM CONFIGURATION DIRECTORY for all users.
These files are YAML files with the following YAML keys: :sources: A YAML array of remote gem repositories to install gems from :verbose: Verbosity of the gem command.
The Marshal version number comes from ruby’s Marshal:: MAJOR_VERSION and Marshal:: MINOR_VERSION constants. Provide help on the ‘gem’ command The install command installs local or remote gem into a gem repository.