Peter H. FröhlichI am messing around with creating my own .deb files and slapping together my own roughly Debian-shaped apt repository. The plan is to fill it with #NoAI packages that were built using #NoAI compilers and libraries. I am not at all sure if I am really the person to be doing this, but surely SOMEBODY must start? Or maybe this is already in progress elsewhere and once again I don't know about it?
I did not think I'd get podman to work on an old RPi 3 from 2015 but hey, it's-a-buildin' openrsync via an Alpine Linux 3.16.3 container and it's generating a static ARM64 executable that runs natively on the "Raspberry Pi OS" on the host so ... I guess I am reasonably happy?
It's REAL SLOOOOOW though. 😞
This presumably means that I can generate .deb files for ARM64 as well as AMD64 and hence host a repository for at least two architectures. Not going to try to stretch beyond, this is good enough for the #NoAI work.
And I guess openrsync will be the first "product" to test the whole process with.
Not super-happy about the containers BUT it's really the simplest way to ensure that people can replicate the builds if they really want to. Seems hard to explain how to set up EXACTLY the same build environment to get bit-by-bit identical binaries without containers. 🤷
I have no good story yet for the source code though. Seems silly to package it inside the .deb file but pointing to a commit in some git repo, possibly on a terrible site like github, that's kind of dubious too. Put up git mirrors on codeberg? Host .tar.gz checkouts of the commit that was built? Not real sure...