almalinux/pungi
14
1
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
2,011 Commits 3 Branches 366 Tags 9.2 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
41e144e47d
Go to file
Marek Marczykowski-Górecki 41e144e47d Use $SOURCE_DATE_EPOCH (if set) in discinfo file 
This helps the output image to be reproducible.

Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
2018-10-08 13:33:29 +02:00
bin ostree: Fix handler crash without commit ID 2018-09-19 13:07:03 +02:00
contrib/yum-dnf-compare gather: Only parse pungi log once 2017-08-09 11:04:14 +02:00
doc Add 'pkgset_koji_builds' option to include extra builds in a compose 2018-09-21 14:06:49 +02:00
pungi Use $SOURCE_DATE_EPOCH (if set) in discinfo file 2018-10-08 13:33:29 +02:00
pungi_utils unified_isos: Add extra variants to metadata 2018-10-05 12:01:43 +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 extra_iso: Add list of variants to metadata 2018-10-05 12:01:43 +02:00
.gitignore Log PDC communications and info for modular composes 2017-10-27 16:20:21 +02: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 Use Python 3 print function 2017-08-23 09:41:22 +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 Extract only first version from specfile 2017-03-06 09:08:13 +01:00
MANIFEST.in Stop shipping and remove RELEASE-NOTES 2018-09-13 10:30:17 +01:00
pungi.spec 4.1.28 release 2018-09-06 13:43:04 +02:00
README.md Add README 2016-03-08 16:38:40 +01:00
setup.py 4.1.28 release 2018-09-06 13:43:04 +02:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
tox.ini Ignore more pycodestyle warnings 2017-06-14 13:21:31 +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.

Links