An InstalledSpecification represents a gem that is already installed locally.
A LocalSpecification comes from a .gem file on the local filesystem.
The LockSpecification comes from a lockfile (Gem::RequestSet::Lockfile).
A LockSpecification’s dependency information is pre-filled from the lockfile.
The RequirementList is used to hold the requirements being considered while resolving a set of gems.
The RequirementList acts like a queue where the oldest items are removed first.
The SourceSet chooses the best available method to query a remote index.
Kind off like BestSet but filters the sources for gems
The Resolver::SpecSpecification contains common functionality for Resolver specifications that are backed by a Gem::Specification.
A Resolver::Specification contains a subset of the information contained in a Gem::Specification. Only the information necessary for dependency resolution in the resolver is included.
A VendorSpecification represents a gem that has been unpacked into a project and is being loaded through a gem dependencies file through the path: option.
Gem::Security default exception type
A source representing a single .gem file. This is used for installation of local gems.
An absolutely silent IO.
Gem::Resolver::Molinillo is a generic dependency resolution algorithm.
A generic resource abstract class.
Error raised when no cdylib artifact was created
Converts Ruby link flags into something cargo understands
A state that encapsulates a single possibility to fulfill the given {#requirement}
Provides information about specifications and dependencies to the resolver, allowing the {Resolver} class to remain generic while still providing power and flexibility.
This module contains the methods that users of Gem::Resolver::Molinillo must to implement, using knowledge of their own model classes.
Delegates all {Gem::Resolver::Molinillo::SpecificationProvider} methods to a ‘#specification_provider` property.