Results for: "fnmatch"

No documentation available

Processes the topmost available {RequirementState} on the stack @return [void]

@return [ResolutionState] the state whose ‘requirement` is the given

`requirement`.

Ensures there are no orphaned successors to the given {vertex}. @param [DependencyGraph::Vertex] vertex the vertex to fix up. @return [void]

@return [Boolean] whether the current spec is satisfied as a new possibility.

(see Gem::Resolver::Molinillo::SpecificationProvider#requirement_satisfied_by?)

No documentation available

In case we’re building docs in a background process, this method waits for that process to exit (or if it’s already been reaped, or never happened, swallows the Errno::ECHILD error).

No documentation available

@return [Integer] The index to which the resolution should unwind in the

case of conflict.

Attempts to swp the current {#possibility} with the already-activated spec with the given name @return [Boolean] Whether the possibility was swapped into {#activated}

Pushes a new {DependencyState} that encapsulates both existing and new requirements @param [Array] new_requirements @return [void]

No documentation available
No documentation available

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]

Ensures any raised {NoSuchDependencyError} has its {NoSuchDependencyError#required_by} set. @yield

Search took: 3ms  ·  Total Results: 2041