Test that "rich" repositories defined as dicts in the configuration stay as dicts in the arguments passed to the osbuild phase. Signed-off-by: Tomáš Hozza <firstname.lastname@example.org> (cherry picked from commit
|6 months ago|
|contrib/yum-dnf-compare||6 years ago|
|doc||6 months ago|
|pungi||6 months ago|
|pungi_utils||3 years ago|
|share||6 years ago|
|tests||6 months ago|
|.gitignore||2 years ago|
|AUTHORS||7 years ago|
|COPYING||7 years ago|
|GPL||8 years ago|
|MANIFEST.in||5 years ago|
|Makefile||3 years ago|
|README.md||2 years ago|
|TODO||9 years ago|
|git-changelog||4 years ago|
|pungi.spec||11 months ago|
|requirements.txt||11 months ago|
|setup.py||11 months ago|
|test-requirements.txt||3 years ago|
|tox.ini||1 year ago|
Pungi is a distribution compose tool.
Composes are release snapshots that contain release deliverables such as:
- installation trees
- (bootable) ISOs
- kickstart trees
- anaconda images
- images for PXE boot
Pungi consists of multiple separate executables backed by a common library.
The main entry-point is the
pungi-koji script. It loads the compose
configuration and kicks off the process. Composing itself is done in phases.
Each phase is responsible for generating some artifacts on disk and updating
compose object that is threaded through all the phases.
Pungi itself does not actually do that much. Most of the actual work is delegated to separate executables. Pungi just makes sure that all the commands are invoked in the appropriate order and with correct arguments. It also moves the artifacts to correct locations.