almalinux/pungi
15
2
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
2,942 Commits 3 Branches 369 Tags 8.3 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
53c273f025
Go to file
Adam Williamson 53c273f025 move osbuild/kiwi-specific EXTENSIONS to each phase 
The image-build phase's EXTENSIONS dict is meant to exactly
mirror the 'formats' that exist in the context of the command
`koji image-build`, which is driven by this phase. That nice
association was lost, however, by adding a couple of items to it
which exist for the purposes of the osbuild phase (and in the
case of .iso, also the kiwibuild phase), which import this dict
and uses it for image identification.

To make the association 1:1 again and more clearly show what's
going on here, let's move those entries out into the osbuild and
kiwi phases. osbuild now has its own dict which starts out as a
copy of the image-build one before being extended. And let's
update the relevant comments.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
(cherry picked from commit 5338d3098ccd614a8fd32f837a393aed78b471bd)
2025-09-29 18:15:18 +03:00
contrib Add config file for cleaning up cache files 2023-11-10 16:51:51 +02:00
doc kiwibuild: Allow setting metadata type explicitly 2025-09-29 18:15:17 +03:00
pungi move osbuild/kiwi-specific EXTENSIONS to each phase 2025-09-29 18:15:18 +03:00
pungi_utils Fix formatting of long line 2024-08-30 13:39:51 +03: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 kiwibuild: Allow setting metadata type explicitly 2025-09-29 18:15:17 +03:00
.gitignore nomacboot option for livemedia koji tasks 2022-03-23 09:36:51 +01:00
1860.patch Release 4.10.1 2025-09-29 18:14:47 +03: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 git-changelog: Fix running on Python 3 2019-07-02 15:05:25 +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 Use pytest instead of nosetests 2020-07-29 14:57:16 +08:00
MANIFEST.in Default bztar format for sdist command 2023-11-10 16:50:33 +02:00
pungi.spec Release 4.10.1 2025-09-29 18:14:47 +03:00
README.md Correct irc network name & add matrix room 2021-10-25 07:26:18 +00:00
requirements.txt Clean up requirements 2024-08-30 13:40:02 +03:00
setup.cfg Default bztar format for sdist command 2023-11-10 16:50:33 +02:00
setup.py Release 4.7.0 2024-08-30 13:40:54 +03:00
sources Release 4.10.1 2025-09-29 18:14:47 +03:00
test-requirements.txt Install unittest2 only on python 2 2024-08-30 13:39:26 +03:00
TODO Drop buildinstall method 2024-08-30 13:30:35 +03:00
tox.ini Clean up requirements 2024-08-30 13:40:02 +03: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