Introduce multilib-devel container

Can be used to build 32bit (aka multilib) packages. With all the
simplification and de-duplication done with the previous commits, this
turns out to be a fairly simple job ;-)

Notes:
 - there is currently no test stage for this container
 - the release bits will come with next commit

v2:
 - preserve extra.conf for base/base-devel

Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>

.gitlab-ci.yml

@@ -60,7 +60,7 @@ get_version:
   stage: rootfs
   parallel:
     matrix:
-      - GROUP: [base, base-devel]
+      - GROUP: [base, base-devel, multilib-devel]
   before_script:
     - pacman -Syu --noconfirm git make fakechroot fakeroot
     - pacman -Sdd --noconfirm devtools
@@ -97,7 +97,7 @@ rootfs:secure:
   stage: image
   parallel:
     matrix:
-      - GROUP: [base, base-devel]
+      - GROUP: [base, base-devel, multilib-devel]
   tags:
     - vm
   before_script:

Makefile

@@ -16,6 +16,6 @@ $(OUTPUTDIR)/Dockerfile.%: $(OUTPUTDIR)/%.tar.zst
 
 # The following is for local builds only, it is not used by the CI/CD pipeline
 
-all: image-base image-base-devel
+all: image-base image-base-devel image-multilib-devel
 image-%: $(OUTPUTDIR)/Dockerfile.%
 	${OCITOOL} build -f $(OUTPUTDIR)/Dockerfile.$(*) -t archlinux/archlinux:$(*) $(OUTPUTDIR)

README.md

@@ -12,8 +12,9 @@ Arch Linux provides OCI-Compliant container images in multiple repositories:
 * [Daily in our ghcr.io repository][ghcr-containers]:
 `podman pull ghcr.io/archlinux/archlinux:latest` or `docker pull ghcr.io/archlinux/archlinux:latest`
 
-Two versions of the image are provided: `base` (approx. 150 MiB) and `base-devel`
+Three versions of the image are provided: `base` (approx. 150 MiB), `base-devel`
-(approx. 260 MiB), containing the respective meta package. Both are available as
+(approx. 260 MiB) and `multilib-devel` (approx. 300MiB) containing the
+respective meta package. All of them are available as
 tags with `latest` pointing to `base`. Additionally, images are tagged with their
 date and build job number, f.e. `base-devel-20201118.0.9436`.
 
@@ -32,7 +33,8 @@ $ cosign verify ghcr.io/archlinux/archlinux:latest --certificate-identity-regexp
 
 ## Principles
 * Provide the Arch experience in a Docker image
-* Provide the simplest but complete image to `base` and `base-devel` on a regular basis
+* Provide the simplest but complete image to `base`, `base-devel` and
+`multilib-devel` on a regular basis
 * `pacman` needs to work out of the box
 * All installed packages have to be kept unmodified
 
@@ -63,9 +65,9 @@ Install the following Arch Linux packages:
 Make sure your user can directly interact with Podman (i.e. `podman info` works).
 
 ### Usage
-Run `make image-base` to build the `archlinux:base` image with the `base` meta
+There are multiple `make image-XXX` targets, where each creates the
-package installed. You can also run `make image-base-devel` to build the image
+respective `archlinux:XXX` image based on the corresponding meta package.
-`archlinux:base-devel` which additionally has the `base-devel` group installed.
+Currently those include `base`, `base-devel` and `multilib-devel`.
 
 ## Pipeline
 

scripts/make-rootfs.sh

@@ -12,7 +12,8 @@ mkdir -vp "$BUILDDIR/alpm-hooks/usr/share/libalpm/hooks"
 find /usr/share/libalpm/hooks -exec ln -sf /dev/null "$BUILDDIR/alpm-hooks"{} \;
 
 mkdir -vp "$BUILDDIR/var/lib/pacman/" "$OUTPUTDIR"
-install -Dm644 /usr/share/devtools/pacman.conf.d/extra.conf "$BUILDDIR/etc/pacman.conf"
+[[ "$GROUP" == "multilib-devel" ]] && pacman_conf=multilib.conf || pacman_conf=extra.conf
+install -Dm644 "/usr/share/devtools/pacman.conf.d/$pacman_conf" "$BUILDDIR/etc/pacman.conf"
 cat pacman-conf.d-noextract.conf >> "$BUILDDIR/etc/pacman.conf"
 
 sed 's/Include = /&rootfs/g' < "$BUILDDIR/etc/pacman.conf" > pacman.conf