The utility for building of AlmaLinux distributions (repos, ISO images).
e043604822
Update pungi-make-ostree to supourt sub-command 'tree', which is just as the original feature of pungi-make-ostree to compose OSTree tree. With the change we can add other sub commands later to build other OSTree artifacts, like the installer image. Inaddtional to the change, now the the 'tree' command can accept an optional '--extra-config' parameter to update the original tree configuration with extra configurations specified in a json file before composing the OSTree tree. Example: pungi-make-ostree tree --repo=/ostree --treefile=/path/to/treefile \ --log-dir=/path/to/log --extra-config=/path/to/extra-config.json The extra-config file can contains the same configuration as OSTree phase, the difference is it doesn't understand variant UID as source repo since it's not ran in the chain of phases. A valid configuration can be like: { "source_repo_from": "http://example.com/repo/x86_64/Server", "extra_source_repos": [ { "name": "optional", "baseurl": "http://example.com/repo/x86_64/optional", "exclude": "systemd-container", "gpgcheck": False }, { "name": "extra", "baseurl": "http://example.com/repo/x86_64/extra", } ], "keep_original_sources": True } The OSTree phase is updated to move out the task of updating treefile, instead of that, it writes the extra configurations to a json file, then 'pungi-make-ostree tree' will take it by option '--extra-config'. Signed-off-by: Qixiang Wan <qwan@redhat.com> |
||
---|---|---|
bin | ||
doc | ||
pungi | ||
share | ||
tests | ||
.gitignore | ||
AUTHORS | ||
COPYING | ||
git-changelog | ||
GPL | ||
Makefile | ||
MANIFEST.in | ||
pungi.spec | ||
README.md | ||
RELEASE-NOTES | ||
setup.py | ||
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
- Upstream GIT: https://pagure.io/pungi/
- Issue tracker: https://pagure.io/pungi/issues
- Questions can be asked on #fedora-releng IRC channel on FreeNode