Skip to content

add support for boot-deploy hooks

Administrator requested to merge master into master

Hooks can be used to run scripts after boot-deploy's source_* commands.

Example use case

Some devices use QCDT for packing the devicetree blob, and boot-deploy expects the file to be in /boot/dt.img. The dt.img is usually generated in the kernel APKBUILD, but for a kernel which is meant for multiple of such devices (such as a mainline kernel), it is not possible to determine the target device.

The only viable option is to use some form of a script which is executed before boot-deploy attempts to create the boot.img. The script will have access to deviceinfo and thus can access device parameters.

Sample output
# boot-deploy ...
==> Running hooks
=> Found compatible entry: samsung,a6lte
    (chip: 7870, hw_rev: 3, hw_rev_end: 255)
==> initramfs: creating boot.img
==> Checking free space at /boot
... OK!
==> Installing: /boot/initramfs
==> Installing: /boot/initramfs-extra
==> Installing: /boot/boot.img
Edited by Administrator

Merge request reports