mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-27 16:51:12 -07:00
Every image records the identity of its build inputs. forgefirm-manifest.bbclass gives a component recipe a per-file source fingerprint (git ls-tree blob ids, submodules recursed; file:// sources hashed with git hash-object); the kernel and glowforge.ko publish theirs through do_deploy because kernel-module-split leaves the module recipe's main package empty. forgefirm-image-manifest.bbclass assembles the entries with the platform identity - machine, modules directory, device tree hashes, layer content hashes (meta-forgefirm and the meta-openglow layers by content, the kas-managed layers by revision) - into /etc/forgefirm-manifest.json and deploys a copy next to the image. Layer revisions and dirty flags stay outside the identity, so a rebuild from an unchanged tree keeps its content hash and the release and dev images of one build share it. The acceptance tool and the release gate read this file.
19 lines
888 B
Plaintext
19 lines
888 B
Plaintext
# ForgeFIRM image manifest: source fingerprint of glowforge.ko.
|
|
#
|
|
# kernel-module-split packages the .ko into a versioned package that the
|
|
# recipe's main package only RPROVIDES, so a rootfs file installed here
|
|
# would never reach the image. The entry is deployed instead; the image
|
|
# collects it from DEPLOY_DIR_IMAGE (forgefirm-image-manifest.bbclass).
|
|
inherit forgefirm-manifest deploy
|
|
FORGEFIRM_MANIFEST_MODE = "deploy"
|
|
|
|
python do_deploy() {
|
|
import os
|
|
entry = forgefirm_manifest_entry(d)
|
|
forgefirm_manifest_write(entry, os.path.join(d.getVar('DEPLOYDIR'), 'forgefirm-manifest.d',
|
|
d.getVar('PN') + '.json'))
|
|
}
|
|
do_deploy[vardeps] += "FORGEFIRM_MANIFEST_NAME SRCREV SRC_URI forgefirm_manifest_entry \
|
|
forgefirm_manifest_tree forgefirm_manifest_git forgefirm_manifest_write"
|
|
addtask deploy after do_install before do_build
|