Returns true and prepares http response, if rdoc for the requested gem name pattern was found.
The search is based on the file system content, not on the gems metadata. This allows additional documentation folders like ‘core’ for the Ruby core documentation - just put it underneath the main doc folder.
Return the best specification that contains the file matching path amongst the specs that are not activated.
Thanks, FakeWeb!
Creates a self-signed certificate with an issuer and subject of subject and the given extensions for the key.
Creates a self-signed certificate with the given number of bits, the issuer cn and a comment to be stored in the certificate.
Creates a self-signed certificate with the given number of bits, the issuer cn and a comment to be stored in the certificate.
Pushes a new {DependencyState}. If the {#specification_provider} says to {SpecificationProvider#allow_missing?} that particular requirement, and there are no possibilities for that requirement, then ‘state` is not pushed, and the node in {#activated} is removed, and we continue resolving the remaining requirements. @param [DependencyState] state @return [void]
Whether to expect full paths in default gems - true for non-MRI ruby implementations
Is there a path from ‘self` to `other` following edges in the dependency graph? @return true iff there is a path following edges within this {#graph}
Sets up the resolution process @return [void]
@return [Conflict] a {Conflict} that reflects the failure to activate
the {#possibility} in conjunction with the current {#state}
Indicates progress roughly once every second @return [void]