The utility for building of AlmaLinux distributions (repos, ISO images).
Go to file
2023-11-10 21:38:01 +02:00
contrib Add config file for cleaning up cache files 2023-11-10 16:51:51 +02:00
doc 4.5.0 release 2023-11-10 16:58:03 +02:00
pungi - Properly removing tmp files 2023-11-10 21:38:01 +02:00
pungi_utils Drop pungi-orchestrator code 2023-11-10 16:54:40 +02:00
share Allow setting <kojitag/> in <modules/> in variants.xml to get the modules from this Koji tag. 2018-03-21 14:33:45 +01:00
tests - The unittests are fixed 2023-11-10 18:08:03 +02:00
.gitignore nomacboot option for livemedia koji tasks 2022-03-23 09:36:51 +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 git-changelog: Fix running on Python 3 2019-07-02 15:05:25 +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 Use pytest instead of nosetests 2020-07-29 14:57:16 +08:00
MANIFEST.in Default bztar format for sdist command 2023-11-10 16:50:33 +02:00
pungi.spec - New upstream release 4.5.0 2023-11-10 16:47:04 +02:00
README.md Correct irc network name & add matrix room 2021-10-25 07:26:18 +00:00
requirements.txt Add support for not having koji volume mounted locally 2023-11-10 16:55:19 +02:00
setup.cfg Default bztar format for sdist command 2023-11-10 16:50:33 +02:00
setup.py 4.5.0 release 2023-11-10 16:58:03 +02:00
test-requirements.txt Use requirements.txt 2020-08-11 20:36:22 +08:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
tox.ini Involve bandit 2022-04-07 14:03:57 +08: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.