The utility for building of AlmaLinux distributions (repos, ISO images).
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
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
7 years ago
bin Add JSON Schema for configuration 7 years ago
doc extra-files: Write a metadata file enumerating extra files 7 years ago
pungi extra-files: Write a metadata file enumerating extra files 7 years ago
share Allow specifying empty variants 8 years ago
tests extra-files: Write a metadata file enumerating extra files 7 years ago
.gitignore Update makefile targets for testing 8 years ago
AUTHORS extra-files: Write a metadata file enumerating extra files 7 years ago
COPYING Initial changes for Pungi 4.0. 9 years ago
GPL Update GPL to latest version from https://www.gnu.org/licenses/gpl-2.0.txt 8 years ago
MANIFEST.in include tests/fixtures in manifest 8 years ago
Makefile Allow arbitrary arguments in make test 7 years ago
README.md Add README 8 years ago
RELEASE-NOTES Rename product_* to release_*. 8 years ago
TODO Initial code merge for Pungi 4.0. 9 years ago
git-changelog Allow running scripts with any python in PATH 8 years ago
pungi.spec Add JSON Schema for configuration 7 years ago
setup.py Add JSON Schema for configuration 7 years ago
tox.ini Ignore module imports not at top of file 7 years ago

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.