* Parse `pkgname` from `PKGBUILD` via sourcing to cope with variables
* Allow overriding the container name to be able to re-use an existing
container
* Be verbose when installing packages during the image creation
The current approach was not actually working as the container was not
start with in interactive bash shell (or any kind of process that would
just keep it running once started).
* Test with `podman` and add according instructions
* Allow use of a custom `pacman.config`/`makepkg.config` by mounting them
into a special directory within the container
* Add my GPG key to the pacman keyring (not nice to hard-code it in the
Dockerfile but good enough for now)
* Install ccache into the base image to support makepkg's ccache option
* Split syncing packages and execution of `makepkg` so syncing can be
avoided when only building source package
* Don't quote `CRE`, it is unlikely spaces are needed here and using
chained commands (e.g. `sudo …`) might be useful
* Add documentation
* Allow building Arch Linux packages within a "standard" container similar
to how `makechrootpkg` allows building packages within a systemd-nspawn
container
* Add a Dockerfile to create an Arch Linux image suitable for package
builds via `makepkg`
We must not link statically against it because it is also pulled by the
shared GLX library and would therefore end up multiple times in the apps
address space causing crashes. It should be stable enough anyways to not
having to bundle it. Since 1.6.x is still the newest version on older
distributions we must downgrade the version, though.
* Use an older glibc so resulting binaries can run
on older systems (without having to link statically
against glibc)
* Call packages static-compat-* to make it clear that
these packages are intended for compatibility with
older distributions
* Add further libraries to get static-compat-qt6-base
and some other static-compat-qt6-* packages building