The utility for building of AlmaLinux distributions (repos, ISO images).
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Lubomír Sedlář d6dc269ef4 Remove FSF address from comments
The address is no longer correct. We can just as well simply point to
the web page describing the license.

Signed-off-by: Lubomír Sedlář <>
7 years ago
bin Remove FSF address from comments 7 years ago
doc Update contributing guide 7 years ago
pungi Remove FSF address from comments 7 years ago
share variants: Allow multiple explicit optional variants 7 years ago
tests init: Remove keep_original_comps option 7 years ago
.gitignore Update makefile targets for testing 8 years ago
AUTHORS extra-files: Write a metadata file enumerating extra files 7 years ago
COPYING Remove FSF address from comments 7 years ago
GPL Update GPL to latest version from 8 years ago include tests/fixtures in manifest 8 years ago
Makefile Allow arbitrary arguments in make test 7 years ago Add README 8 years ago
RELEASE-NOTES Rename product_* to release_*. 8 years ago
TODO Initial code merge for Pungi 4.0. 9 years ago
git-changelog Allow running scripts with any python in PATH 8 years ago
pungi.spec 4.1.9 release 7 years ago 4.1.9 release 7 years ago
tox.ini Ignore module imports not at top of file 7 years ago


Pungi is a distribution compose tool.

Composes are release snapshots that contain release deliverables such as:

  • installation trees
    • RPMs
    • repodata
    • comps
  • (bootable) ISOs
  • kickstart trees
    • anaconda images
    • images for PXE boot

Tool overview

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 the 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.