The utility for building of AlmaLinux distributions (repos, ISO images).
Go to file
Patrick Uiterwijk 2c401a4a5c Send fedmsg message on ostree compose finishg
This sends a message when we finish composing an ostree.

Signed-off-by: Patrick Uiterwijk <puiterwijk@redhat.com>
2016-09-15 11:16:18 +00:00
bin Allow user to set a ~/.pungirc for some defaults 2016-09-08 15:47:50 +02:00
doc createrepo: Add option to use xz compression 2016-09-12 11:10:43 +02:00
pungi Send fedmsg message on ostree compose finishg 2016-09-15 11:16:18 +00:00
share Allow specifying empty variants 2016-02-16 15:08:15 +01:00
tests createrepo: Add option to use xz compression 2016-09-12 11:10:43 +02:00
.gitignore Update makefile targets for testing 2016-02-23 13:03:11 +01:00
AUTHORS extra-files: Write a metadata file enumerating extra files 2016-09-07 13:02:48 +02:00
COPYING Initial changes for Pungi 4.0. 2015-02-10 06:47:16 -05:00
git-changelog Allow running scripts with any python in PATH 2015-11-27 08:38:47 +01:00
GPL Update GPL to latest version from https://www.gnu.org/licenses/gpl-2.0.txt 2015-06-25 07:50:03 -04:00
Makefile Allow arbitrary arguments in make test 2016-09-01 10:49:36 +02:00
MANIFEST.in include tests/fixtures in manifest 2016-04-29 21:11:01 -05:00
pungi.spec Add JSON Schema for configuration 2016-09-01 10:56:15 +02:00
README.md Add README 2016-03-08 16:38:40 +01:00
RELEASE-NOTES Rename product_* to release_*. 2015-07-09 06:58:30 -04:00
setup.py Add JSON Schema for configuration 2016-09-01 10:56:15 +02:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
tox.ini Ignore module imports not at top of file 2016-08-22 10:55:48 +02:00

Pungi

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.