The utility for building of AlmaLinux distributions (repos, ISO images).
081c31238b
This patch connects the phase into the main script, and adds other modifications: * The archive is now stored in the images/ subdirectory in the compose. * Documentation is updated to correctly mention that variant repos are not available. * Configuration for path and name of the final archive is dropped. There are reasonable defaults for this and there's no point in having users configure it. * The extra message for the archive is no longer sent. * The pungi-make-ostree utility is no longer required in the buildroot. The pungi-make-ostree utility doesn't do any significant work. It modifies configuration files (which can happen on the compose host), and it starts other processes. This patch changes the ostree-container phase to no longer need the script in the buildroot. Instead, the utility is called on the compose host to do the config manipulation and output the needed commands. Those are then passed into the runroot task. Signed-off-by: Lubomír Sedlář <lsedlar@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