almalinux/pungi
15
1
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
2,133 Commits 3 Branches 365 Tags 9.1 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
66a127c313
Go to file
Lubomír Sedlář 66a127c313 pkgset: Refactor hiding unused modular packages 
A module build can create packages that are tagged in the content tag,
but should not be included in the module. Originally Pungi didn't know
what exactly the module contains and so it needed to apply filters to
exclude stuff that was definitely out.

With getting the final MMD from Koji, we can actually make this a bit
more strict by only keeping packages that we know we need.

When processing each content tag, we can put into package set only
packages that are included in some module using that tag. This should
work with -devel modules as well. Both the regular and -devel modules
will contribute to the set and thus all packages will go to the package
set.

Signed-off-by: Lubomír Sedlář <lsedlar@redhat.com>
2019-03-25 08:48:16 +01:00
bin orchestrator: Send messages about the main compose 2019-03-21 09:29:54 +01:00
contrib/yum-dnf-compare gather: Only parse pungi log once 2017-08-09 11:04:14 +02:00
doc buildinstall: Allow overwriting version for lorax 2019-03-22 12:47:16 +01:00
pungi pkgset: Refactor hiding unused modular packages 2019-03-25 08:48:16 +01:00
pungi_utils orchestrator: Send messages about the main compose 2019-03-21 09:29:54 +01: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: Refactor hiding unused modular packages 2019-03-25 08:48:16 +01: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 Add script to orchestrate multiple composes 2019-01-08 09:40:36 +01:00
MANIFEST.in Include all test fixtures in source tarball 2018-10-17 10:09:46 +02:00
pungi.spec 4.1.34 release 2019-03-05 12:37:07 +01:00
README.md README: add link to documentation 2019-02-18 14:36:48 -07:00
setup.py 4.1.34 release 2019-03-05 12:37:07 +01: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