Tags: dist
-
System Model
The model is deliberately layered. Configuration expresses intent, the database records owned state, and the public tree is a deterministic projection. None of those layers may quietly become a substitute for another. Object hierarchy Workspace ├── …
The model is deliberately layered. Configuration expresses intent, the database records owned state, and the public tree is a deterministic projection. None of those layers may quietly become a substitute for another. Object hierarchy Workspace ├── …
-
sow export
SOW provides one export subcommand: sow export rpm-leaf. It creates an external, standalone RPM repository whose repodata uses local pool/... hrefs. Synopsis sow export rpm-leaf DIST ARCH DIR [--hardlink] [-C|--workdir DIR] [-r|--repo NAME] [--json] …
SOW provides one export subcommand: sow export rpm-leaf. It creates an external, standalone RPM repository whose repodata uses local pool/... hrefs. Synopsis sow export rpm-leaf DIST ARCH DIR [--hardlink] [-C|--workdir DIR] [-r|--repo NAME] [--json] …
-
sow dist
A Dist is a named set of packages in exactly one format (rpm or deb) inside one Repository. It is what a client points at. A Repository can hold RPM and DEB Dists side by side; they share one pool/ but render into completely separate dists/ subtrees. …
A Dist is a named set of packages in exactly one format (rpm or deb) inside one Repository. It is what a client points at. A Repository can hold RPM and DEB Dists side by side; they share one pool/ but render into completely separate dists/ subtrees. …
-
Pool & Metadata Views
The invariant Within one Repository, every live Package Object has one canonical payload path under pool/. Dists and architecture views own metadata, not aliases of package bytes: <repo>/pool/... canonical package payloads …
The invariant Within one Repository, every live Package Object has one canonical payload path under pool/. Dists and architecture views own metadata, not aliases of package bytes: <repo>/pool/... canonical package payloads …
-
Repository Layout
SOW has one fixed Managed layout: package payloads live once under pool/, while dists/ contains metadata-only client views. The complete repository directory is the unit to serve, copy, or publish. Plain mode sow create writes indexes next to …
SOW has one fixed Managed layout: package payloads live once under pool/, while dists/ contains metadata-only client views. The complete repository directory is the unit to serve, copy, or publish. Plain mode sow create writes indexes next to …
-
Core Concepts
Plain or Managed The two execution paths are separate. Plain Managed Entry point sow create DIR init, repo, dist, add, rm, build State package directory sow.yml plus private SQLite/journals Public layout flat RPM/DEB indexes Repository pool/ + dists/ …
Plain or Managed The two execution paths are separate. Plain Managed Entry point sow create DIR init, repo, dist, add, rm, build State package directory sow.yml plus private SQLite/journals Public layout flat RPM/DEB indexes Repository pool/ + dists/ …
-
Managed Workspaces
Managed mode is what you use when the same repository will be updated for months: packages arrive in batches, policy decides what stays, and you need to prove afterwards what changed and when. This page explains the three-tier model, the layout it …
Managed mode is what you use when the same repository will be updated for months: packages arrive in batches, policy decides what stays, and you need to prove afterwards what changed and when. This page explains the three-tier model, the layout it …
-
Your First Workspace
Managed mode keeps configuration, membership, generations, and audit state. This example starts from an empty directory. Initialize the workspace sow init /srv/sow cd /srv/sow init creates: /srv/sow/ ├── sow.yml # configuration; schema: sow/v3 └── …
Managed mode keeps configuration, membership, generations, and audit state. This example starts from an empty directory. Initialize the workspace sow init /srv/sow cd /srv/sow init creates: /srv/sow/ ├── sow.yml # configuration; schema: sow/v3 └── …
-
Build an APT Repository
This tutorial creates a new Managed DEB repository. You need a writable directory, and one or more DEB files. 1. Create the workspace mkdir -p /srv/sow cd /srv/sow sow init . sow repo new pigsty sow dist new trixie --format deb -r pigsty The Dist …
This tutorial creates a new Managed DEB repository. You need a writable directory, and one or more DEB files. 1. Create the workspace mkdir -p /srv/sow cd /srv/sow sow init . sow repo new pigsty sow dist new trixie --format deb -r pigsty The Dist …
-
Build a YUM Repository
This tutorial creates a new Managed RPM repository. You need a writable directory, and one or more RPM files. 1. Create the workspace mkdir -p /srv/sow cd /srv/sow sow init . sow repo new pigsty sow dist new el9 --format rpm -r pigsty The Dist name …
This tutorial creates a new Managed RPM repository. You need a writable directory, and one or more RPM files. 1. Create the workspace mkdir -p /srv/sow cd /srv/sow sow init . sow repo new pigsty sow dist new el9 --format rpm -r pigsty The Dist name …