graywolf on Nostr: npub1p5fhs…lu6aj npub19amud…hqjn6 This was quite interesting read, and the VM ...
npub1p5fhs5atqhjmeu023zwe94v85dl76sp66a0hkhhk66k049dn0ccsylu6aj (npub1p5f…u6aj) npub19amud7rggjx0u77wqqa84x537x7g5nws9pqdgu5qadgypfreyv2s5hqjn6 (npub19am…qjn6) This was quite interesting read, and the VM solution is fairly elegant.
I wonder whether it would be possible to add CPU, date, ... fields to the package record type and, iff set, automatically spawn VM for the build of that specific package.
For the "In rare cases, there’s software influenced by kernel details not controlled by the build daemon", another one I encountered is that currently python (Guix package) does not build when Guix runs on a foreign distro Alpine linux.
I wonder whether it would be possible to add CPU, date, ... fields to the package record type and, iff set, automatically spawn VM for the build of that specific package.
For the "In rare cases, there’s software influenced by kernel details not controlled by the build daemon", another one I encountered is that currently python (Guix package) does not build when Guix runs on a foreign distro Alpine linux.