The utility for building of AlmaLinux distributions (repos, ISO images).
Go to file
Lubomír Sedlář a31be0a3c4 Fix test data build script
It uses bash specific features, so it should not claim /bin/sh in
shebang. We also want to use `set -e` to catch possible errors instead
of claiming success every time.

Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
2016-09-01 08:46:23 +02:00
bin [createiso] Remove unused script 2016-08-30 10:28:18 +02:00
doc Update doc about generating release value 2016-08-26 10:05:25 +02:00
pungi [osbs] Add NVRA of created image into main log 2016-08-30 10:37:17 +02:00
share Allow specifying empty variants 2016-02-16 15:08:15 +01:00
tests Fix test data build script 2016-09-01 08:46:23 +02:00
.gitignore Update makefile targets for testing 2016-02-23 13:03:11 +01:00
AUTHORS Initial changes for Pungi 4.0. 2015-02-10 06:47:16 -05: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 Update makefile targets for testing 2016-02-23 13:03:11 +01:00
MANIFEST.in include tests/fixtures in manifest 2016-04-29 21:11:01 -05:00
pungi.spec 4.1.8 release 2016-08-10 07:21:40 -05: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 [createiso] Remove unused script 2016-08-30 10:28:18 +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.