* Use `--userns` to become `builduser` right away instead of using `sudo`
to become `builduser`
* Add `builduser` to `sudoers` so it can become root to synchronize
packages
* Ensure this way that files created within the container have the
user/group of the user starting the container so build artifacts have the
right ownership
This is useful to invoke `updpkgsums` or `repo-add` within the container as
well. These tools also seem to need the additional logic to use a dedicated
build user so it makes sense to make this part of `makecontainerpkg`.
* 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`
Martchus