Package

Go to Terms and Definitions

A Package is a composite Artifact assembled and distributed as an identifiable unit.

A Package may contain one or more Artifacts together with metadata needed to identify, verify, install, load, configure, or use the Package.

A Package commonly has:

• name
• version
• producer or supplier
• package format
• manifest or other descriptive metadata
• One or more dependencies
• cryptographic digest
• digital signature
• Installation, loading, or use instructions

A Package may be produced internally or delivered by a third party.

Different versions of a Package constitute different managed versions of the same Package. A Package version may also have multiple Artifact Representations for different operating systems, processor architectures, or package formats.

A Package remains distinct from a Bundle. A Package is independently identified and distributed as a unit, while a Bundle may assemble selected Packages and other Artifacts for a defined delivery, deployment, or operational purpose.

composite Artifact assembled and distributed as an identifiable unit

Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

A Package is an Artifact, but not every Artifact is a Package.

A Package may contain other Artifacts without changing the identities of those Artifacts.

The term does not require a particular package manager, archive format, repository product, operating system, or implementation technology.

A Package stored or referenced by Crucible is described by an Artifact Catalog Record.

A third-party PostgreSQL RPM containing executable files, software libraries, configuration content, dependency metadata, and installation information is a Package.

Separate RPMs (i.e., package manager) built for Red Hat Enterprise Linux on x86-64 and ARM64 are distinct Artifact Representations of the applicable Package version.