There is an updated pull request by Piraty against master on the void-packages repository https://github.com/Piraty/void-packages rpi-kernel-flavor-subpackage https://github.com/void-linux/void-packages/pull/26000 [NEEDS TESTERS] rpi-kernel: build a subpackage for each flavor, add rpi4 This enables building all Raspberry Pi kernels from a single template by using individual builddir/destdir for each flavor and performing all stages independently with help of the `_flavor_stage()` function. * rpi-kernel is a meta package now that is built by default for every arch and continues to serve legacy installations as it depends on the respective (former one-per-arch) rpi{1,2,3}-kernel package. * subpackages are enabled conditionally for each arch. * add rpi4 see: https://github.com/void-linux/void-mklive/pull/153 as well @Duncaen @pbui --- ### How to Build packages ``` cd void-packages ./xbps-src -m masterdir.rpi4 binary-bootstrap ./xbps-src -m masterdir.rpi4 -a aarch64-musl pkg rpi-base ./xbps-src -m masterdir.rpi4 -a aarch64-musl pkg rpi-kernel ``` Build images (from branch https://github.com/void-linux/void-mklive/pull/153) ``` cd void-mklive d=$(date '+%Y%m%d') repo=$(xdistdir)/hostdir/binpkgs/ make XBPS_REPOSITORY="-r $repo" void-aarch64-musl-ROOTFS-$d.tar.xz void-rpi3-musl-$d.img.xz void-rpi4-musl-$d.img.xz ``` --- ### Remaining issues - [ ] change to `rpi-base` require manual action for existing instals (`rpi{0,1,2,3}`). (rpi-kernel will result in an orphan) is there a better way? A patch file from https://github.com/void-linux/void-packages/pull/26000.patch is attached