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']
Find
the best specification matching a name
and requirements
. Raises if the dependency doesn’t resolve to a valid specification.
Return the best specification that contains the file matching path
.
Make sure the YAML specification is properly formatted with dashes
Returns the full path to the build info directory
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.
Finds all gems that satisfy dep
TODO: move to minitest
TODO: move to minitest
Allows the proper version of rake
to be used for the test.
Choose from a list of options. question
is a prompt displayed above the list. list
is a list of option strings. Returns the pair [option_name, option_index].
Given the path to a gem file, validates against its own MD5 checksum
Path to gem file
Defines a command, registering path
as a Shell
method for the given command
.
Shell::CommandProcessor.def_system_command "ls" #=> Defines ls. Shell::CommandProcessor.def_system_command "sys_sort", "sort" #=> Defines sys_sort as sort
Undefines a command
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.