almalinux/pungi
15
2
Fork 0
Code Issues Pull Requests Releases Activity
The utility for building of AlmaLinux distributions (repos, ISO images).
1,264 Commits 3 Branches 369 Tags 8.3 MiB
Python 99.4%
XSLT 0.3%
Shell 0.2%
Makefile 0.1%
ee1ee0467b
Go to file
Jeremy Cline ee1ee0467b extra-files: Write a metadata file enumerating extra files 
Introduces a new metadata file to track arbitrary files added during the
extra-files phase. This file is placed in the root of each tree and is
called ``extra_files.json``. It is a JSON file containing a single
object, which contains a "header" key with an object describing the
metadata, and a "data" key, which is an array of objects, where each
object represents a file. Each object contains the "file", "checksums",
and "size" keys. "file" is the relative path from the tree root to the
extra file. "checksums" is an object containing one or more checksums,
where the key is the digest type and the value of that key is the hex
digest. Finally, the size is the size of the file in bytes.

For example:
{
  "header": {"version": "1.0},
  "data": [
    {
      "file": "GPL",
      "checksums": {
        "sha256": "8177f97513213526df2cf6184d8ff986c675afb514d4e68a404010521b880643"
      },
      "size": 18092
    },
    {
      "file": "release-notes/notes.html",
      "checksums": {
        "sha256": "82b1ba8db522aadf101dca6404235fba179e559b95ea24ff39ee1e5d9a53bdcb"
      },
      "size": 1120
    }
  ]
}

Signed-off-by: Jeremy Cline <jeremy@jcline.org>
Fixes: #295
2016-09-07 13:02:48 +02:00
bin Add JSON Schema for configuration 2016-09-01 10:56:15 +02:00
doc extra-files: Write a metadata file enumerating extra files 2016-09-07 13:02:48 +02:00
pungi extra-files: Write a metadata file enumerating extra files 2016-09-07 13:02:48 +02:00
share Allow specifying empty variants 2016-02-16 15:08:15 +01:00
tests extra-files: Write a metadata file enumerating extra files 2016-09-07 13:02:48 +02:00
.gitignore Update makefile targets for testing 2016-02-23 13:03:11 +01:00
AUTHORS extra-files: Write a metadata file enumerating extra files 2016-09-07 13:02:48 +02:00
COPYING Initial changes for Pungi 4.0. 2015-02-10 06:47:16 -05:00
git-changelog Allow running scripts with any python in PATH 2015-11-27 08:38:47 +01: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 Allow arbitrary arguments in make test 2016-09-01 10:49:36 +02:00
MANIFEST.in include tests/fixtures in manifest 2016-04-29 21:11:01 -05:00
pungi.spec Add JSON Schema for configuration 2016-09-01 10:56:15 +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 Add JSON Schema for configuration 2016-09-01 10:56:15 +02:00
TODO Initial code merge for Pungi 4.0. 2015-02-10 08:19:34 -05:00
tox.ini Ignore module imports not at top of file 2016-08-22 10:55:48 +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