Differences

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

Link to this comparison view

Both sides previous revision Previous revision
public:99_annexes:annex-b-terms-and-definitions:p:package [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:p:package to public:99_annexes:annex-b-terms-and-definitions:p:package nick_didopublic: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 ====== ====== Package ======
  
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]+[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
  
-A Package is a composite [[private:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] assembled and distributed as an identifiable unit.+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 may contain one or more Artifacts together with metadata needed to identify, verify, install, load, configure, or use the Package.
Line 23: Line 23:
 A Package may be produced internally or delivered by a third party. 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 [[private:99_annexes:annex-b-terms-and-definitions:a:artifact_catalog_record|Artifact Representations]] for different operating systems, processor architectures, or package formats.+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. 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.
Line 43: Line 43:
 The term does not require a particular package manager, archive format, repository product, operating system, or implementation technology. 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 [[private:99_annexes:annex-b-terms-and-definitions:a:artifact_catalog_record|Artifact Catalog Record]].+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 ===== ===== Example =====
  • public/99_annexes/annex-b-terms-and-definitions/p/package.1789260161.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido