The utility for building of AlmaLinux distributions (repos, ISO images).
Go to file
Lubomír Sedlář 079cc46458 pungi: Fix reading multilib config files
When running from git, the files should be found relative to the python
module, not executable itself. This change makes it possible to load the
files when running tests.

Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
2016-11-09 09:36:23 +01:00
bin pungi: Add tests for depsolving 2016-11-09 09:36:23 +01:00
doc Update ostree phase documentation 2016-11-04 09:35:08 +01:00
pungi pungi: Fix reading multilib config files 2016-11-09 09:36:23 +01:00
share variants: Allow multiple explicit optional variants 2016-09-19 12:21:19 +02:00
tests pungi: Fulltree should not apply for input multilib package 2016-11-09 09:36:23 +01: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 Replace mount/umount with guestfsmount and 'fusermount -u' 2016-10-20 19:38:35 +08: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.