community/pacman: makepkg subpackage breaks pacman-key

The recently introduced pacman-makepkg sub-package contains libraries that are used also by at least pacman-key, which is part of the main pacman package and also needed to get pacman up-and-running at all (at least in the common use case, I would say).

Here is a log from my system, demonstrating the issue with a valid pacman config, without the pacman-makepkg package installed:

alpine-dev:~# pacman -Sw filesystem
resolving dependencies...

Packages (2) iana-etc-20220715-1  filesystem-2021.12.07-1

Total Download Size:  0.40 MiB

:: Proceed with download? [Y/n] y
:: Retrieving packages...
 filesystem-2021....    14.5 KiB   145 KiB/s 00:00 [######################] 100%
 iana-etc-2022071...   394.9 KiB  1579 KiB/s 00:00 [######################] 100%
 Total (2/2)           409.4 KiB  1516 KiB/s 00:00 [######################] 100%
(2/2) checking keys in keyring                     [######################] 100%
warning: Public keyring not found; have you run 'pacman-key --init'?
downloading required keys...
error: keyring is not writable
error: keyring is not writable
error: required key missing from keyring
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.
alpine-dev:~# pacman-key --init
/usr/bin/pacman-key: line 31: /usr/share/makepkg/util/message.sh: No such file or directory
/usr/bin/pacman-key: line 32: /usr/share/makepkg/util/parseopts.sh: No such file or directory
/usr/bin/pacman-key: line 620: parseopts: command not found
alpine-dev:~#

Installing pacman-makepkg fixes the issue (lets me run pacman-key, which in turn makes pacman work).

Given this, I am wondering if the split of the pacman-makepkg makes sense at all?