almalinux/pungi
14
1
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
4 Commits 3 Branches 366 Tags 9.2 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
478018f6f2
Go to file
oshyshatskyi 478018f6f2 LNX-102: Add tool that gathers directory for all rpms 
Tool that finds all available rpm files in directory
and creates special tree for pungi:
 # ls /mnt/koji/
   i686/  noarch/  x86_64/

Change-Id: Ibcf2d23c46411ad89477058f4d56e07ca117f0d1
2021-01-12 06:33:03 -05:00
contrib/yum-dnf-compare init commit 2021-01-08 15:56:32 +03:00
doc init commit 2021-01-08 15:56:32 +03:00
pungi LNX-102: Add tool that gathers directory for all rpms 2021-01-12 06:33:03 -05:00
pungi_utils init commit 2021-01-08 15:56:32 +03:00
share init commit 2021-01-08 15:56:32 +03:00
tests LNX-102: Add tool that gathers directory for all rpms 2021-01-12 06:33:03 -05:00
.gitignore init commit 2021-01-08 15:56:32 +03:00
AUTHORS init commit 2021-01-08 15:56:32 +03:00
COPYING init commit 2021-01-08 15:56:32 +03:00
git-changelog init commit 2021-01-08 15:56:32 +03:00
GPL init commit 2021-01-08 15:56:32 +03:00
Makefile init commit 2021-01-08 15:56:32 +03:00
MANIFEST.in init commit 2021-01-08 15:56:32 +03:00
pungi.spec LNX-103 Update .spec file for AlmaLinux 2021-01-11 14:56:04 +03:00
README.md init commit 2021-01-08 15:56:32 +03:00
requirements.txt init commit 2021-01-08 15:56:32 +03:00
setup.py LNX-102: Add tool that gathers directory for all rpms 2021-01-12 06:33:03 -05:00
test-requirements.txt init commit 2021-01-08 15:56:32 +03:00
TODO init commit 2021-01-08 15:56:32 +03:00
tox.ini init commit 2021-01-08 15:56:32 +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