almalinux/pungi
14
1
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
2,870 Commits 3 Branches 366 Tags 7.4 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
57f2b428d5
Go to file
Adam Williamson 57f2b428d5
kiwibuild: allow setting description scm and path at phase level 
Neal wanted this to work - he tried using global_description_scm
and global_description_path in the initial PR - but it wasn't
wired up to work. This should make it possible to set
`kiwibuild_description_scm` and `kiwibuild_description_path`.
It also technically lets you set `global_` for both, since the
`get_config` implementation is very generic, but it doesn't add
it to the checks, so you'd still get an "unrecognized config
option" warning, I think. It seems appropriate to encourage
setting this as a phase-level option rather than a global one
since it seems quite specific to the kiwibuild phase.

Merges: https://pagure.io/pungi/pull-request/1737
Signed-off-by: Adam Williamson <awilliam@redhat.com>
(cherry picked from commit e90ffdfd93)
2024-08-30 13:39:29 +03:00
contrib Add config file for cleaning up cache files 2023-11-10 16:51:51 +02:00
doc Release 4.6.2 2024-08-30 13:39:22 +03:00
pungi kiwibuild: allow setting description scm and path at phase level 2024-08-30 13:39:29 +03:00
pungi_utils Drop pungi-orchestrator code 2023-11-10 16:54:40 +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 Use latest Fedora for python 3 test environment 2024-08-30 13:39:28 +03:00
.gitignore nomacboot option for livemedia koji tasks 2022-03-23 09:36:51 +01:00
1715.patch Backport: Stop requiring repo option in ostree phase 2024-08-30 13:26:39 +03: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 git-changelog: Fix running on Python 3 2019-07-02 15:05:25 +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 Use pytest instead of nosetests 2020-07-29 14:57:16 +08:00
MANIFEST.in Default bztar format for sdist command 2023-11-10 16:50:33 +02:00
pungi.spec New upstream release 4.7.0 2024-08-30 13:29:32 +03:00
README.md Correct irc network name & add matrix room 2021-10-25 07:26:18 +00:00
requirements.txt Add support for not having koji volume mounted locally 2023-11-10 16:55:19 +02:00
setup.cfg Default bztar format for sdist command 2023-11-10 16:50:33 +02:00
setup.py Release 4.6.2 2024-08-30 13:39:22 +03:00
sources New upstream release 4.7.0 2024-08-30 13:29:32 +03:00
test-requirements.txt Install unittest2 only on python 2 2024-08-30 13:39:26 +03:00
TODO Drop buildinstall method 2024-08-30 13:30:35 +03:00
tox.ini Update tox configuration 2024-08-30 13:31:28 +03: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