almalinux/pungi
14
1
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
1,720 Commits 3 Branches 366 Tags 9.2 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
04836cfa9f
Go to file
Lubomír Sedlář 04836cfa9f docs: Mention how input package list are interpreted 
It's really just an RPM name, not any random provide or source package
name.

Fixes: https://pagure.io/pungi/issue/725
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
2017-09-18 12:06:03 +02:00
bin Fix pungi-koji --version 2017-09-18 17:04:05 +08:00
contrib/yum-dnf-compare gather: Only parse pungi log once 2017-08-09 11:04:14 +02:00
doc docs: Mention how input package list are interpreted 2017-09-18 12:06:03 +02:00
pungi profiler: Fix sorting on Python 3 2017-09-13 09:55:51 +02:00
pungi_utils unified-iso: Only link to non-empty variants 2017-07-31 15:15:17 +02:00
share Add support for modular composes 2017-03-22 15:55:52 +01:00
tests Fix pungi-koji --version 2017-09-18 17:04:05 +08: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 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 setup: Update manifest to include doc images 2017-07-17 09:26:20 +02:00
pungi.spec log: save imported config files too 2017-09-08 16:39:38 +08: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 Check for correct string class 2017-08-28 14:31:09 +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