Started configuring buildroot on my way home via my phone. Protip, don't do that through Termux - it's actually terrible with this xD I wish I have had some kind of gesture controls... Termux is, for all intends and purposes, an "okay" terminal emulator. But once you need to do more than type short commands, it falls apart so fast o.o

Basically, what I am planning to do:

FROM scratch AS buildroot

ADD buildroot-rootfs.tar.gz /

FROM buildroot AS buildroot-apk

ADD abuild.tar.gz /

ADD apk-static.tar.gz /

COMMAND ["/bin/sh"]

This can now be used to put together any abuild-based package ... including Alpine, itself. Now all I have left to do is to automate the building of this, split it into actual containers (buildroot:$version and buildroot-apk:$version) and then use the latter to start building the entirity of Alpine 3.19's rootfs, start to finish and more packages as I am going.

Since I have a kernel config, I will edit that to become modular instead so that I can build kernel module packages, vendor-prefix that so it doesn't collide (i.e. linux-image-vf2ip for VisionFive2 Ingwie Phoenix) and then ... send it. A week or two later, I should have a complete build of Alpine 3.19, that I can then install into a docker container as a new rootfs, and publish, and use for any other container that happens to rely on it. Oh and notify the Alpine guys about it.

Last thing to do is to learn how to automate all of this with Jenkins. I got my configs, I got my storage, and I got my host. So ... let's go!

Oh and while I am at it, I might start making strfry images with complete static linkage and a single layer. The faster we can deploy Nostr tools everywhere, the better. This is effectively a side product. x)

i.e.:

FROM buildroot-apk as build

RUN apk install --no-cache $strfry_dev_deps

RUN make setup-golpe && make -j$(nprocs)

FROM scratch

COPY --from=build .../strfry /strfry

ENTRYPOINT ["/strfry"]

This'd be freaking neat - and it IS possible. PRing that into upstream will be wild. :D