The utility for building of AlmaLinux distributions (repos, ISO images).
Go to file
2017-06-20 15:27:38 +00:00
bin Add dropped livemedia phase 2017-06-19 08:58:53 +02:00
contrib/yum-dnf-compare Add scripts to compare YUM and DNF gathering 2017-03-24 09:24:46 +01:00
doc docs: Kobo can be installed via pip now 2017-06-20 11:11:16 +02:00
pungi gather: Log tag from which we pulled a package 2017-06-19 10:51:37 +02:00
pungi_utils unified-iso: Use different type for debuginfo iso 2017-04-06 09:08:08 +02:00
share Add support for modular composes 2017-03-22 15:55:52 +01:00
tests gather: Log tag from which we pulled a package 2017-06-19 10:51:37 +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 Remove FSF address from comments 2016-09-23 10:26:43 +02:00
git-changelog Fix changelog generator script 2017-06-08 11:00:22 +02: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 Extract only first version from specfile 2017-03-06 09:08:13 +01:00
MANIFEST.in Make MANIFEST.in stricter 2017-03-03 14:01:50 +08:00
pungi.spec 4.1.16 release 2017-06-09 13:12:19 +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 4.1.16 release 2017-06-09 13:12:19 +02:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
tox.ini Ignore more pycodestyle warnings 2017-06-14 13:21:31 +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.