The utility for building of AlmaLinux distributions (repos, ISO images).
Go to file
Dennis Gilmore 5c4d3a5196 [createiso] Add back running isohybrid on x86 disk images
rhbz#1331317 when we refactored how we make dvds in
df400002d8 we lost the ability to boot
the dvd as a disk image.

Signed-off-by: Dennis Gilmore <dennis@ausil.us>
2016-04-29 09:00:44 +02:00
bin 4.1.3 release 2016-04-08 07:34:57 -05:00
doc [ostree-installer] Drop filename setting 2016-04-14 14:45:36 +02:00
pungi [createiso] Add back running isohybrid on x86 disk images 2016-04-29 09:00:44 +02:00
share Allow specifying empty variants 2016-02-16 15:08:15 +01:00
tests [createiso] Add back running isohybrid on x86 disk images 2016-04-29 09:00:44 +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 4.0.5 release 2016-02-23 12:08:33 -06:00
pungi.spec 4.1.3 release 2016-04-08 07:34:57 -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 4.1.3 release 2016-04-08 07:34:57 -05:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
tox.ini Update makefile targets for testing 2016-02-23 13:03:11 +01: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.