The utility for building of AlmaLinux distributions (repos, ISO images).
cfb7b71fca
- Pass the runroot_tag to init command in OpenSSH Runroot method. This is needed for the init command as a source for initial packages for the buildroot. - Rename the "runroot_ssh_init_command" to "runroot_ssh_init_template" to make it consistent with the rest of "runroot_ssh_*" options. - Add missing "runroot_ssh_*" options to checks.py. - Use chmod/chown to `output_dir` in OpenSSH Runroot method the same way as it is used in Koji runroot method to make the runroot output readable for Pungi user. Signed-off-by: Jan Kaluza <jkaluza@redhat.com> |
||
---|---|---|
bin | ||
contrib/yum-dnf-compare | ||
doc | ||
pungi | ||
pungi_utils | ||
share | ||
tests | ||
.gitignore | ||
AUTHORS | ||
COPYING | ||
git-changelog | ||
GPL | ||
Makefile | ||
MANIFEST.in | ||
pungi.spec | ||
README.md | ||
setup.py | ||
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 on #fedora-releng IRC channel on FreeNode