The utility for building of AlmaLinux distributions (repos, ISO images).
Go to file
Adam Williamson c321bca8ef image_build: fix subvariant handling
Dennis added a 'subvariant' property to the Docker image config,
but we weren't using it, we were just hard-coding the variant
as the subvariant...and doing it wrong, as well, using the
variant object rather than its uid property.

This fixes both problems: we'll now use the explicitly set
image config 'subvariant' property if there is one, otherwise
we use the variant.uid as the subvariant.

Note this is a high priority fix, as it broke F24 compose today.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
2016-03-13 09:18:08 -07:00
bin [checks] Don't always require jigdo 2016-03-10 09:08:19 +01:00
doc [init] Update documentation 2016-03-10 15:42:21 +01:00
pungi image_build: fix subvariant handling 2016-03-13 09:18:08 -07:00
share Allow specifying empty variants 2016-02-16 15:08:15 +01:00
tests Remove check for disc type 2016-03-11 08:55:21 +01:00
.gitignore Update makefile targets for testing 2016-02-23 13:03:11 +01:00
AUTHORS Initial changes for Pungi 4.0. 2015-02-10 06:47:16 -05:00
COPYING Initial changes for Pungi 4.0. 2015-02-10 06:47:16 -05: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
MANIFEST.in 4.0.5 release 2016-02-23 12:08:33 -06:00
Makefile Update makefile targets for testing 2016-02-23 13:03:11 +01:00
README.md Add README 2016-03-08 16:38:40 +01:00
RELEASE-NOTES Rename product_* to release_*. 2015-07-09 06:58:30 -04:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
git-changelog Allow running scripts with any python in PATH 2015-11-27 08:38:47 +01:00
pungi.spec 4.1.0 dev start 2016-02-23 12:19:59 -06:00
setup.py 4.1.0 dev start 2016-02-23 12:19:59 -06:00
tox.ini Update makefile targets for testing 2016-02-23 13:03:11 +01: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.