packaging: Add kernel-install hook for booster
This allows booster to be used as the initrd_generator with kernel-install (1).
Any objections for this change? If not - I am going to merge it to the codebase.
I think mkinitcpio and dracut include microcode in their generated initramfs, and I know booster purposely doesn't.
So presumably for mkinitcpio/dracut folks, microcode gets applied as expected, but using kernel-install with this booster hook will ignore microcode entirely.
Wondering if this hook could/should include something to make sure any ucode files get included in the bootloader entry? E.g. checking for *-ucode.img files in /boot and copying them to the output directory
Edit: Typo on line 24? "Thres is an [...]", maybe meant to be "There is an [...]"?
Edit 2: 50-dracut.install and 50-mkinitcpio.install I think both run after 50-depmod.install (assuming it's alphabetical), but 50-booster.install seems to run before -- should it be 60-booster.install instead?
@anatol Could you merge this and get it into a release? I plan to write up kernel-install support for Arch Linux at some point in the future.
@Foxboron merged now
@anatol Thanks!