almalinux/pungi
14
1
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
1,995 Commits 3 Branches 366 Tags 9.2 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
fbb739ef17
Go to file
Lubomír Sedlář fbb739ef17 pkgset: Apply whitelist to modules in the tag 
This patch changes the behaviour when both module tag and NSV?C? is
specified. The NSVC are used as a whitelist and only matching modules
will be included in the compose.

Additionally this patch adds filtering based on inheritance: when
finding the latest module for each N:S combination, only the top tag in
which the module is tagged is used. Even if a newer build is available
somewhere deeper in the inheritance, it's not going to be used.

Example inheritance and tagged modules

    f29-compose (foo:1:2018:cafe)
    └─ f29-candidate (foo:1:2019:cafe)

The compose will use 2018 version, because it's in the topmost tag.

JIRA: COMPOSE-2685
Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
2018-09-03 12:19:50 +02:00
bin ostree: Wait for updated ref as well as signature 2018-09-03 09:54:12 +02:00
contrib/yum-dnf-compare gather: Only parse pungi log once 2017-08-09 11:04:14 +02:00
doc pkgset: Apply whitelist to modules in the tag 2018-09-03 12:19:50 +02:00
pungi pkgset: Apply whitelist to modules in the tag 2018-09-03 12:19:50 +02:00
pungi_utils Stop using deprecated pipes.quote 2017-10-24 15:15:31 +02:00
share Allow setting <kojitag/> in <modules/> in variants.xml to get the modules from this Koji tag. 2018-03-21 14:33:45 +01:00
tests pkgset: Apply whitelist to modules in the tag 2018-09-03 12:19:50 +02:00
.gitignore Log PDC communications and info for modular composes 2017-10-27 16:20:21 +02:00
AUTHORS extra-files: Write a metadata file enumerating extra files 2016-09-07 13:02:48 +02:00
COPYING Remove FSF address from comments 2016-09-23 10:26:43 +02:00
git-changelog Use Python 3 print function 2017-08-23 09:41:22 +02: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
Makefile Extract only first version from specfile 2017-03-06 09:08:13 +01:00
MANIFEST.in Include all test data in tarball 2018-08-17 09:34:56 +02:00
pungi.spec Use dogpile.cache to cache the listTaggedRPMS calls if possible 2018-08-30 13:21:01 +02: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
setup.py Use dogpile.cache to cache the listTaggedRPMS calls if possible 2018-08-30 13:21:01 +02:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
tox.ini Ignore more pycodestyle warnings 2017-06-14 13:21:31 +02: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