Is is ok to remove a gemspec from the dependency list?
If removing the gemspec creates breaks a currently ok dependency, then it is NOT ok to remove the gemspec.
Removes the gemspec matching full_name from the dependency list
List of gem file names to index.
Writes the full .gemspec specification (in Ruby) to the gem home’s specifications/default directory.
Ensures the Gem::Specification written out for this gem is loadable upon installation.
Prefix and suffix the program filename the same as ruby.
Writes the .gem file to the cache directory
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']
Returns the full path to the file containing the build information generated when the gem was installed
Sets extra_rdoc_files to files, ensuring it is an array. Don’t use this, push onto the array instead.
Expire memoized instance variables that can incorrectly generate, replace or miss files due changes in certain attributes used to compute them.
Installs the provided default specs including writing the spec file
Install the provided default specs
Given the path to a gem file, validates against its own MD5 checksum
Path to gem file
Reads bytes from filename and adds them to the PRNG.
Writes a number of random generated bytes (currently 1024) to filename which can be used to initialize the PRNG by calling ::load_random_file in a later session.
define methodname as instance method of current module, using ERB object or eRuby file
define methodname as instance method of current module, using ERB object or eRuby file
@return the next sibling (nil if unset)