I have a couple of things I'm working on with the image-builder:* Cape support: I need a way to get dtbo loaded at boot, preferably without custom kernel (e.g. via initrd or by putting the .dtbo's in mmcblp0p1)
For the latter, at your suggestion, I forked the repo and created my own myimage_image.sh by copying beagleboard.org_image.sh. However, you've been busy ... *too* busy and I'm way behind on merging in your changes!It looks like you're working to a more extensible scheme for customizations, I see the machinekit configuration now has a directory with custom scripts in it, along with the machinekit() function in releases.sh.This looks pretty interesting, it would be kind of cool to be able to do:./image_builder.sh "myimage"And have it raid the ./myimage" directory to get the configuration, package lists etc. for the "myimage" build.How far off is this? I'd love to help test this out.
I don't have any personal plans to do that yet. If you look closely, all the frontend scripts do is create a ".project" file and call ./RootStock-NG.sh... If you want to make something universal generic, go ahead.. All generic options should end up in the main chroot call with "enable" options passed thru .project and anything target specific should end up under target/