...into mixins to make the distro configuration
more reusable and portable across target arches.
Think grafting instead of just growing from seed.

See-also: ba437ba8

Signed UEFI loader not required for aarch64.

NB: i586 images don't need UEFI SB either
and 32-bit shim is used for x86_64 images
along with proper 64-bit one.

GRUB is available on several target platforms for us,
but the particular package needed will vary.

This reverts commit 1b457a5d.
It wasn't prudent to switch everyone to master FTP server;
Yandex mirror still has an order of magnitude more bandwidth.

ttyAMA0 needed for qemu on aarch64 and armh.
ttySI0 needed for HiFive Unleashed (riscv64).

...and drop duplication tossed in by i-f-online-repo.

See-also: https://bugzilla.altlinux.org/36952

%_host_cpu was a wrong choice in the first place,
and the particular case of %_arch == ppc64le
with %_host_cpu == powerpc64le became the culprit.

The problem is that `chkconfig dm on' will enable
display manager service on *all* runlevels feasible
without paying any attention to its customary subset
of those; the solution seems just to avoid that.

Note that there's at least one more similar case
with networking services vs runlevels 2 and 3;
it's to be handled either in a similar manner,
or somewhat more generically.

Reported-by: Konstantin Savun and Speccyfighter
Suggested-by: Anton Midyukov <antohami@altlinux.org>
See-also: https://bugzilla.altlinux.org/36967
See-also: https://forum.altlinux.org/index.php?topic=36177.msg340553#msg340553
See-also: https://www.opennet.ru/openforum/vsluhforumID3/117762.html#81

As noted in the previous commit,
it's just not making it now.

It's actually sisyphus jeos image that needed this:
open-vm-tools got installed and then removed just
before the final reboot (unlike p8 jeos); not clear
what exactly caused this as subsequent installation
only pulled in libdnet and libicu56, neither of which
were excplicitly removed during cleanup.

Let's make the image a bit leaner until someone asks
for VMware support there.

Suggested by Speccyfighter:
https://forum.altlinux.org/index.php?topic=36177.msg340161#msg340161

Allow placing profiles in directory like groups and lists.

These packages have long been empty and are being removed from Sisyphus.

These packages have long been empty and are being removed from Sisyphus.

- add server-v profile, drop groups/openstack (shaba@)

We've decided that there's not much sense to continue building
server-openstack flavour of starterkits since it does take quite
an effort to even test properly, and there was rather no feedback
on those (maybe silent users will at least ping back this time).

Those interested are invited to follow server-v development
and contact Alexey Shabalin <shaba@altlinux.org> for cooperation.

PS: the actual pkglists are here, it's only the bunch of groups
tailored for standalone server-openstack with its group selection
menu layout that are being removed regarding the shared bits.

Removed from sisyphus, actually:
http://git.altlinux.org/tasks/archive/done/_197/202601/

- uboot feature, bootloader refactoring, etc (antohami@)
- cleanlog factored out from reports.mk (me)

sddm doesn't work with sysvinit currently, so this
mixin is not a good place to specify the display manager;
and different platforms may have different needs,
e.g. sddm has just stopped working on aarch64 boards.

Sometimes REPORT=1 just wasn't passed to make, and the build.log
saved is noisy and harder to compare through diff(1); let's move
the implementation out of the makefile and into a standalone
script so it can be reused like this:

  BUILDDIR=$(sed -rn "s/^mki-image-scripts: export GLOBAL_BUILDDIR='(.*)'$/\1/p" build/build.log
  bin/cleanlog < build/build.log > build/reports/clean.log

See "export GLOBAL_BUILDDIR=" line in the particular log
(grabbing that one from stdin is not exactly trivial though).

$GRUB_ARCHES is the list of GRUB 2 supported architectures

Add target use/bootloader/uboot. Das U-Boot -- the Universal Boot
Loader, used on single board PCs (also in qemu).

Use bootloader lists to provide better portability and to avoid
overcomplicating bootloader switch.

Added restriction for alterator-$$(BASE_BOOTLOADER)) only for
ISO images. Since the new uboot bootloader is not supported in
Alterator and is not used when building ISO images.