WIP: Add Fedora/Archlinux build in CI

[Tristan971]

Hi, off the back of a short exchange of Discord, here's a proof of concept / WIP on how to check that Ladybird continues building on a few popular non-Ubuntu distributions.

Specifically, issues like #2149 and my anecdotal personal experience show that Fedora regularly cannot successfully build Ladybird. And while mentioning some of the issues (other than from the issue linked), @ADKaster on Discord suggested that it was tricky to ensure things kept working because Github does not provide a viable non-Ubuntu host environment, which is fair enough.

Thus this relatively minimal PoC/WIP on how this can still be done:

1. A weekly-scheduled build of a couple of distributions docker images, intended for CI building
2. Running a simple ./Meta/labybird.sh build in those images, whether automatically in the generic CI workflow (probably slow and noisy, but referenced in this PoC for simplicity) or maybe something nightly/weekly

Thoughts and remarks? (I realize there's no effort done with regards to ccache and so on in the current iteration; it can be done, just wanted feedback on the general approach first)

--

NB:

• image building example: https://github.com/Tristan971/ladybird/actions/workflows/distribution-ci-images.yml
• Build-in-distribution-image example: https://github.com/Tristan971/ladybird/actions/workflows/distribution-ci-build.yml

[Tristan971]

For whatever reason, GHCI currently ignores job.container in the last pushes; it definitely ought to work tho, will figure out why later.

[ADKaster]

For whatever reason, GHCI currently ignores job.container in the last pushes; it definitely ought to work tho, will figure out why later.

Presumably you mean on your fork? The CI won't affect this repo until it's merged into master. That's likely true for your fork as well: Things won't be properly hosted on ghcr.io until they are in your master branch

[Tristan971]

Notes after discussing a bit more w/ Andrew on Discord:

1. Probably good to merge the CI image building logic with that of devcontainers so we get double-benefit out of it
2. Make the in-distro-build check a nightly job

[tyzoid]

Wouldn't it make sense for the built images to be in the .pkg.tar.zst or .rpm formats for arch and fedora respectively?

[Tristan971]

This issue is not about providing packages for end users, but rather about testing that Ladybird builds on other Linux distributions than Ubuntu 😅