Use GitHub Actions to build (and host) packages for Ubuntu

[jwakely]

Currently the binary .deb packages are hosted on my personal website. If a GitHub Actions workflow was used to build a new package from the weekly snapshot then the artifacts created from that workflow could be uploaded and hosted on GitHub directly.

This would be more trustworthy than some .deb downloaded from my personal website.

[ilazaric]

Not fully related to the issue, but it might be worth also adding a workflow example on how one can build and cache gcc as part of the workflow.
I've recently started playing around with the WIP gcc reflection implementation, and added it to my CI:
https://github.com/ilazaric/ALL/actions/runs/20649499191/workflow
I'm kinda surprised that it builds pretty fast (only 20min), and doesn't occupy much space in cache (~600MB).

Run without caching: https://github.com/ilazaric/ALL/actions/runs/20649229705/job/59291165449
Run with caching: https://github.com/ilazaric/ALL/actions/runs/20649499191/job/59291786871

Apologies if totally unrelated to the topic at hand, but seemed like a potentially useful data point.

[jwakely]

That seems useful, thanks for the suggestion.

(The reflection branch is likely to be merged to trunk soon-ish, but there will be other development branches in future that people might want to experiment with in CI.)

[jwakely]

It might also be useful to publish a gcc-latest container image to the github container registry:
https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry

That would be slightly quicker and easier to use than copying the Containerfile examples and building a new image.