The utility for building of AlmaLinux distributions (repos, ISO images).
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Go to file
Jan Kaluza 9be2d6a920 Allow setting <kojitag/> in <modules/> in variants.xml to get the modules from this Koji tag.
Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
6 years ago
bin gather: Honor package whitelist 6 years ago
contrib/yum-dnf-compare gather: Only parse pungi log once 6 years ago
doc buildinstall: Add option to disable it 6 years ago
pungi Allow setting <kojitag/> in <modules/> in variants.xml to get the modules from this Koji tag. 6 years ago
pungi_utils Stop using deprecated pipes.quote 6 years ago
share Allow setting <kojitag/> in <modules/> in variants.xml to get the modules from this Koji tag. 6 years ago
tests Allow setting <kojitag/> in <modules/> in variants.xml to get the modules from this Koji tag. 6 years ago
.gitignore Log PDC communications and info for modular composes 6 years ago
AUTHORS extra-files: Write a metadata file enumerating extra files 7 years ago
COPYING Remove FSF address from comments 7 years ago
GPL Update GPL to latest version from https://www.gnu.org/licenses/gpl-2.0.txt 8 years ago
MANIFEST.in setup: Update manifest to include doc images 6 years ago
Makefile Extract only first version from specfile 7 years ago
README.md Add README 8 years ago
RELEASE-NOTES Rename product_* to release_*. 8 years ago
TODO Initial code merge for Pungi 4.0. 9 years ago
git-changelog Use Python 3 print function 6 years ago
pungi.spec 4.1.22 release 6 years ago
setup.py 4.1.22 release 6 years ago
tox.ini Ignore more pycodestyle warnings 6 years ago

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.