Feature kbd remove in make-initrd 2.42.0.

Required mkimage 0.3.0-alt1

glibc can be compiled such that mki-fake-dev requires /proc to works.
This on loongarch64.

rootfs scripts are also run when building live image. But assigning
BASE_BOOTARGS to live is not required, since the arguments are
copied from STAGE1_BOOTARGS by the installer.

check conditions of  make  for equality of variables with an empty value
instead of check definition.
A defined but empty variable under all these conditions results errors.

Chroot can be two or one, work or image.
Package lists of work chroot cannot take into account packages that
will be installed into it after run-scripts.

The definition of the TOPDIR variable has been fixed in a future mkimage.
Will $(TOPDIR)=$(BUILDDIR).

By default, GRUB_TERMINAL_OUTPUT='gfxterm' is configured.
This creates problems for virtual machines and single-board computers,
since they need output to console.

The config for generating a generic initrd can be interesting because
it will allow you to return the initrd to its original generic state.

Variables in cmdline override variables from /etc/initrd.mk
See also: https://lists.altlinux.org/pipermail/make-initrd/2021-September/000533.html

Enable /proc for build vm/<target> and distro/<target> with use/stage2.
/proc needed for make-initrd >= 2.23.0.
See also https://bugzilla.altlinux.org/40900

The commit 99695713 used this variable
even though it didn't exist yet. A good reason to add this variable.

The code is given in accordance with the documentation
See-also: commit 2987fa8f

The parameter is used to save the intermediate tarball used to
build the virtual machine image.

So we are can to build compressed img files.

This is necessary for the 'rootfs' initrd feature to work properly

This is a standard set of initrd features.

This features not needed for auto-detect.
We also add features not only to initrd.mk, but also specify them
explicitly in the command.

While this argument can only have one "EFI" value.
Thus, the problem of building an image for Raspberry Pi on armh,
where there is no grub-efi, was solved.

For Raspberry Pi needed to build grub-efi + MBR images.

The entry in /etc/fstab about the mount parameters of the root
partition needs to be done not only for builds with u-boot.
But, if the record already exists, then it will not be added.
The file system type is set by the variable VM_FSTYPE.

Since packet sorting is enabled by default, then
the order in KFLAVORS has ceased to matter.
Kernels are always installed in alphabetical order.
Therefore, it makes no sense to sort by buildtime.
See-also: https://bugzilla.altlinux.org/show_bug.cgi?id=30806

Also fixed my typo. When creating a symlink, the variable
$kver was used, i.e. the entire list of kernels, not the
last value $KVER of the list.

tar2fs does not run in hasher and without qemu. This causes build
problems for an architecture other than the host.

Not used by systemd and looks obsolete generally
as sysvinit-based disk images aren't really targeting
low-resource systems these days _by default_ but rather
_can_ target those as well; feel free to reconstruct
these "RAM saving" bits as a part of e.g. lowmem patch.

The problem at hand is that different kernels can have
varying module sets, and it makes sense to put four of
those at once sometimes; so avoid silly build breakage.

recovery.tar needed for tavolga (mipsel).
This commit is the result of transferring the required functionality
from build-mr (mipsel rootfs).
This change uses external tool to build Tavolga-compatible
recovery.tar. This simplifies the logic and avoids having
recovery workdir in the profile.
After this change, m-p will require tavolga-image-tools >= 3.0.

KFLAVOURS can describe more than one kernel, get iterator back.

Fixes: 27674e29

(gkebfm@ thinks it was a terrible idea in the first place
and mike@ agrees; this is a rework TODO item)

build-vm ceases to be a target for building only virtual machine images.
Now it can be used to build tarballs designed for installation on real
machines.

This commit is the result of transferring the required functionality from
build-mr (mipsel rootfs) by Ivan Melnikov <iv@altlinux.org>.

NB: mike@ strongly objected to this dilution but gave up eventually;
    the whole kernel/build-vm/tar2fs/pack mess should be split into
    distinct layers busy with their own responsibilities:

    1) a tarball with kernel is done without tar2fs at all
       (and no build-vm bits should be needed either, maybe
       it's worth splitting and renaming as "vm" meaning
       disk image for some armh board is grossly misleading);

    2) a tarball with kernel can be further (multi-)packed
       as, well, (compressed) tarball and a disk image
       (only the latter one should employ build-vm/tar2fs);

    3) compression should be done in pack feature style,
       preferably described once and not duplicated all over
       the profile for every single new kind of its output.

    In the mean time, running into this and moving no further
    starts to hurt more than it could help.

NB: 07-kernel change breaks multi-kernel setup!

Breaks: 650e92bf