The utility for building of AlmaLinux distributions (repos, ISO images).
Go to file
Lubomír Sedlář 1bb1c2ba28 metadata: Treeinfo should point to packages and repo
Each variant section should contain a path to a directory with packages
and to repodata. There was code to do this, but due to a typo it did not
actually work.

Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
2016-10-20 12:05:48 +02:00
bin Dump images.json after checksumming 2016-10-19 15:02:33 +02:00
doc doc: Fix a typo in progress notification example 2016-10-19 15:04:21 +02:00
pungi metadata: Treeinfo should point to packages and repo 2016-10-20 12:05:48 +02:00
share variants: Allow multiple explicit optional variants 2016-09-19 12:21:19 +02:00
tests Merge #433 `createiso: Do not split bootable media` 2016-10-19 16:37:25 +00: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
GPL Update GPL to latest version from https://www.gnu.org/licenses/gpl-2.0.txt 2015-06-25 07:50:03 -04:00
MANIFEST.in include tests/fixtures in manifest 2016-04-29 21:11:01 -05:00
Makefile Create git tags without release 2016-09-27 09:01:13 +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
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
git-changelog Allow running scripts with any python in PATH 2015-11-27 08:38:47 +01:00
pungi.spec 4.1.10 release 2016-10-08 12:15:32 -05:00
setup.py 4.1.10 release 2016-10-08 12:15:32 -05:00
tox.ini Ignore module imports not at top of file 2016-08-22 10:55:48 +02:00

README.md

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.