almalinux/pungi
14
1
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
1,445 Commits 3 Branches 366 Tags 9.2 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
345308464f
Go to file
Lubomír Sedlář 345308464f 4.1.13 release 
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
2017-03-03 14:34:45 +01:00
bin Rename main logger 2017-02-23 11:08:31 +01:00
doc 4.1.13 release 2017-03-03 14:34:45 +01:00
pungi Remove one line of log print 2017-03-02 11:46:33 +08:00
pungi_utils unified-iso: Fall back to default config 2017-01-17 08:15:13 +01:00
share variants: Allow multiple explicit optional variants 2016-09-19 12:21:19 +02:00
tests Merge #539 comps: Filter comps groups for optional variants 2017-02-23 20:13:39 +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
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 Create git tags without release 2016-09-27 09:01:13 +02:00
MANIFEST.in Make MANIFEST.in stricter 2017-03-03 14:01:50 +08:00
pungi.spec 4.1.13 release 2017-03-03 14:34:45 +01: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.13 release 2017-03-03 14:34:45 +01:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
tox.ini Update tox.ini 2017-01-11 14:37:41 +01: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.

Links