Upstream software project

glide

Package Management for Golang

About glide

Package Management for Golang

This project links 2 native package records across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

glide repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 2 package records. Catalog coverage diagram, not an application screenshot.glide: recorded package coverageFedora 432 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
glide
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43
License expression
MIT
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Glide is a tool for managing the vendor directory within a Go package. This feature, first introduced in Go 1.5, allows each package to have a vendor directory containing dependent packages for the project. These vendor packages can be installed by a tool (e.g. glide), similar to go get or they can be vendored and distributed with the package. This package contains the source code needed for building packages that reference the following Go import paths: – github.com/Masterminds/glide

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package glide

    43 (Fedora 43) (Unspecified): Package Management for Golang

    0.13.2-18.fc41: aarch64 x86_64

    Source: glide

  2. Source: glide

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.