It's pretty useless by now IMNSHO given the typical USB flash drive
as the installation media and online repos -- and *seems* to have
problems with flash-based installation:

Running postinstall script [90-pkg.sh] /dev /
/
mount: /media/ALTLinux: /dev/sdb1 already mounted or mount point busy.

...as it rather introduces red ink for no good reason:

Running postinstall script [90-pkg.sh] /dev /
/
mount: /media/ALTLinux: /dev/sdb1 already mounted or mount point busy.

It should do some work: nothing else might have pulled use/x11 in
(which brings another topic to the table: we'd probably better
have some platform-independent targets that pull archdep pieces in
under the hood).

Fixes: 2002e625

Looks like it can get stuck for quite some time on serial ports
that are present and might be occupied by other processes already.

Typing this on an e16c based workstation but 201-PC seems more
likely a target for now.

mpv backend seems to go parallel either with no configuration needed,
or on more media types.

NB: the missing modules break image build,
    avoid mga2/galcore/vivante by default
    (absent in some CPU-specific kernels).

There is no need to set std-def, it is already default on those
architectures where it is available.
Uses package list 'kernel-headers' allows to not depend to specific
kernels.

Add this list if need kernel headers on disk:

	@(call add,MAIN_LISTS,kernel-headers)

The line containing @KFLAVOUR is expanded into several lines,
it is successively replaced with values from the KFLAVOURS variable.
This will allow to specify kernel modules and kernel headers in lists.

Add Environment=GSK_RENDERER=gl for phosh.service.
We switch to the old render, since ngl has a problem with the layout
of layers on Pinephone Pro and other mobile phones.

https://bugzilla.altlinux.org/49741

At the first boot, if there is no network, the wrong time is set,
since the timezone and utc settings occur late.
So at least with the default parameters there will be no problem.

This is an alternative for 80rescue.cfg

Since we check for the presence of a theme before enabling it in
the grub config, it is enough to issue a warning.

GRUB since 93a786a00 (kern/efi/sb: Enforce verification of font files)
has enforced verification of font files in secure boot mode. In order
to continue to be able to load some default fonts, they are added to
the built-in memdisk bundled with a signed EFI image and may be
accessed by file name prior the actual default path.