Masterminds/glide

Features

• Go Dependency Managers - Manages external Go packages by fetching, pinning, and vendoring dependencies for reproducible builds across environments.
• Import Alias Mappings - Maps an import path to a different repository URL, such as a fork, without changing import statements.
• Dependency Lock Managers - Restores the exact dependency tree from a lock file into the vendor directory, skipping already-present packages for speed.
• Dependency Installers - Reads the lock file and installs the exact versions listed, skipping scanning for a fast and deterministic setup.
• Dependency Vendors - Stores project-specific package copies in a vendor directory to avoid version conflicts.
• Lock File Vendors - Downloads all project dependencies into a vendor directory, resolves transitive dependencies, and writes a lock file with exact commit IDs.
• Dependency Declarations - Declares external dependencies in a glide.yaml file, specifying import paths and optional version constraints.
• Dependency Resolvers - Scans source code to identify all external packages and their transitive dependencies for management.
• Dependency Version Wizards - Provides an interactive wizard that scans dependencies and suggests version ranges for configuration.
• Package Dependency Management - Downloads a specified package and its transitive dependencies, then adds it to the configuration file automatically.
• Transitive Dependency Resolution - Scans imported packages recursively to discover and fetch their transitive dependencies.
• Import Path Source Mappings - Maps a dependency to an alternative source, such as a fork, while keeping the original import path.
• Semantic Versioning - Resolves dependency versions using semantic versioning ranges, operators, and lock files for deterministic and reproducible installs.
• Version Constraints - Retrieves a dependency at a version matching a semantic version range, tag, branch, or commit hash from the VCS.
• Dependency Lock Files - Stores exact revision hashes in a glide.lock file to ensure reproducible dependency trees.
• Dependency Isolation - Uses vendor directories to isolate each project's dependency versions and prevent conflicts.
• Semantic Versioning Systems - Works with Semantic Versioning and version ranges to select compatible dependency versions.
• Resolvers - Accepts Semantic Version ranges to specify compatible dependency versions and resolve them automatically.
• Dependency Tree Downloads - Records the full dependency tree and exact revisions for reproducible installations across environments.
• Lock-File Pinning - Generates a glide.lock file that pins every dependency to a specific commit for reproducible installs.
• Dependency Versioning - Restricts acceptable dependency versions using operators like greater-than, less-than, and wildcards.
• Import Path Mapping - Maps import paths to different repository URLs, such as forks, without changing import statements.
• Source Code Dependency Scanners - Scans source code and a configuration file to determine needed packages and retrieves them into the vendor directory.
• Vendor Directory Managers - Stores project-specific copies of Go packages in a vendor directory to isolate dependencies per project.
• Vendor Directories - Stores project-specific copies of Go packages in a vendor directory to isolate dependencies per project.
• Revision Audit Trails - Stores the full dependency tree and commit IDs for review, troubleshooting, and change detection.
• Platform-Specific Restrictions - Limits fetching of a dependency to specific operating systems or architectures using os and arch fields.
• Dependency Configuration Importers - Reads existing dependency configuration from GPM, Godep, Gom, or GB and merges it into a glide.yaml file.
• Dependency Configuration Tools - Walks the filesystem to detect imports and populates a manifest file with external package references and versions.
• Parallel - Installs multiple dependencies and pins their revisions in parallel by using the complete dependency tree for faster setup.
• Test - Lists packages required only during testing, separate from the main import list.
• Conditional Dependency Resolution - Restricts dependency downloads to specific operating systems and architectures using os and arch fields.
• Multi-VCS Package Fetchers - Downloads Go packages from Git, Mercurial, Bazaar, and Subversion repositories into a local vendor tree.
• Manifest Dependency Records - Records dependency information including name, version ranges, and VCS details in a glide.yaml file.
• Dependency Override Managers - Points a dependency to a different repository URL than its import path, enabling forks or private mirrors.
• Package Location Resolvers - Searches vendor directories, GOPATH, and GOROOT in order to locate a dependent package.
• Workspace Initializers - Creates a glide.yaml configuration file by scanning the codebase and importing rules from other package managers.
• Project Initializers - Scans source code and existing package manager config to generate a glide.yaml file with guessed dependencies.
• Cross-VCS Cloning - Supports Git, Bzr, HG, and SVN repositories for fetching dependencies from various VCS backends.
• Architecture Filters - Restricts a dependency to be fetched only when the current CPU architecture matches a listed value.
• Operating System Filters - Restricts a dependency to be fetched only when the current operating system matches a listed value.
• Platform Filters - Restricts a dependency to be fetched only for specified operating systems or CPU architectures.
• Workspace Initializers - Scans the codebase and existing package manager configs to create a glide.yaml file with guessed dependencies and versions.
• Locked Version Updates - Fetches the latest versions matching version ranges and pins exact versions in a lock file.
• Project Dependency Discovery - Scans a Go project's source code and imports dependency configuration from other tools to generate an initial manifest file.
• Multi-VCS Package Fetchers - Downloads Go packages from Git, Mercurial, Bazaar, and Subversion repositories into a local vendor tree.
• Dependency Management - Dependency management inspired by Maven and Bundler.
• Package Management - Dependency management inspired by Maven and Bundler.

Star-Verlauf