Comment # 5 on bug 1202353 from Jiri Slaby

> (In reply to Jiri Slaby from comment #1)
> > @Michal: I do not immediately see why we do:
> > Requires(post): mkinitrd
> 
> Yes, s-m-t should pull in whatever it required to build the ramdisk, the
> kernel does not do it anymore.

Ugh, it apparently doesn't:
$ rpm -q suse-module-tools --requires |sort -u
/bin/bash
/bin/sh
coreutils
findutils
(kmod(sg.ko) if kernel)
rpm
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsZstd) <= 5.4.18-1
rpmlib(RichDependencies) <= 4.12.0-1
systemd-rpm-macros
/usr/bin/grep
/usr/bin/gzip
/usr/bin/perl
/usr/bin/sed

(In reply to Michal Suchanek from comment #4)
> Actually, if we pull in s-m-t, and the kernel gets installed during install
> test will it fail with dracut missing?

It should handle it gracefully (regenerate-initrd-posttrans):
: ${DRACUT:=/usr/bin/dracut}
if [ ! -x "$DRACUT" ]; then
    echo "${0##*/}: dracut is not installed, not rebuilding the initrd" >&2
    exit 0
fi
...
        if ! [  -f /etc/fstab -a ! -e /.buildenv -a -x "$DRACUT" ] ; then
                echo "Please run \"$DRACUT -f --regenerate-all\" as soon as
your system is complete." >&2
                rm "$dir"/*
                exit 0
        fi

> Why do we even BuildIgnore mkinitrd in the first place?

Maybe to avoid dependency loops and avoid creating an initrd during the build
(to speed it up), but who knows...