Converts this AvailableSet into a RequestSet that can be used to install gems.
If development is :none then no development dependencies are installed. Other options are :shallow for only direct development dependencies of the gems in this set or :all for all development dependencies.
Return an array of extra arguments for the command. The extra arguments come from the gem configuration file read at program startup.
Adds extra args from ~/.gemrc
The name of the state file.
Reads time of last update check from state file
Writes time of last update check to state file
True if the gems in the system satisfy dependency.
Writes the full .gemspec specification (in Ruby) to the gem home’s specifications/default directory.
In contrast to write_spec, this keeps file lists, so the ‘gem contents` command works.
Performs various checks before installing the gem such as the install repository is writable and its directories exist, required Ruby and rubygems versions are met and that dependencies are installed.
Version and dependency checks are skipped if this install is forced.
The dependent check will be skipped if the install is ignoring dependencies.
Writes the .gem file to the cache directory
we have our own signing code here to avoid a dependency on the aws-sdk gem
Installs from the gem dependencies files in the :gemdeps option in options, yielding to the block as in install.
If :without_groups is given in the options, those groups in the gem dependencies file are not used. See Gem::Installer for other options.
Extra files to add to RDoc such as README or doc/examples.txt
When the user elects to generate the RDoc documentation for a gem (typically at install time), all the library files are sent to RDoc for processing. This option allows you to have some non-code files included for a more complete set of documentation.
Usage:
spec.extra_rdoc_files = ['README', 'doc/user-guide.txt']