public:99_annexes:annex-b-terms-and-definitions:p:package

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:p:package [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:p:package [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Package ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Package is a composite [[public:99_annexes:annex-b-terms-and-definitions:a:artifact|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 [[public:99_annexes:annex-b-terms-and-definitions:a:artifact_catalog_record|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.
 +
 +===== Definition =====
 +
 +//composite Artifact assembled and distributed as an identifiable unit//
 +
 +===== Source =====
 +
 +Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +===== Note =====
 +
 +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 [[public:99_annexes:annex-b-terms-and-definitions:a:artifact_catalog_record|Artifact Catalog Record]].
 +
 +===== Example =====
 +
 +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.
 +
 +<WRAP centeralign> © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. </WRAP>