The utility for building of AlmaLinux distributions (repos, ISO images).
e90ffdfd93
Neal wanted this to work - he tried using global_description_scm and global_description_path in the initial PR - but it wasn't wired up to work. This should make it possible to set `kiwibuild_description_scm` and `kiwibuild_description_path`. It also technically lets you set `global_` for both, since the `get_config` implementation is very generic, but it doesn't add it to the checks, so you'd still get an "unrecognized config option" warning, I think. It seems appropriate to encourage setting this as a phase-level option rather than a global one since it seems quite specific to the kiwibuild phase. Merges: https://pagure.io/pungi/pull-request/1737 Signed-off-by: Adam Williamson <awilliam@redhat.com> |
||
---|---|---|
contrib | ||
doc | ||
pungi | ||
pungi_utils | ||
share | ||
tests | ||
.gitignore | ||
AUTHORS | ||
COPYING | ||
git-changelog | ||
GPL | ||
Makefile | ||
MANIFEST.in | ||
pungi.spec | ||
README.md | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
TODO | ||
tox.ini |
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
- Documentation: https://docs.pagure.org/pungi/
- Upstream GIT: https://pagure.io/pungi/
- Issue tracker: https://pagure.io/pungi/issues
- Questions can be asked in the #fedora-releng IRC channel on irc.libera.chat
or in the matrix room
#releng:fedoraproject.org