There's no need for bootloader on Elbrus platform
since firmware boots Linux just fine; note that
the whole feature is betted omitted since its
script checks for the case when the feature
is requested but not configured properly.

As the previous commit stated, there's no LibreOffice-still
built for e2k currently.

There's no LibreOffice-still on e2k (no 6.x for now,
just a single production 5.x build); and there's no
office (neither LO nor abiword/gnumeric) at all on
riscv64 as of today.  These nuances shouldn't bother
release managers each time but should lurk under
this feature's cover.

(ftbfs)

There are a few more targets used for Workstation
and Simply images that are rather better plugged
here than patched there.

The culprit is that e2k has exactly one kernel flavour
available at the moment, elbrus-def (there used to be
per-CPU flavours in p8 times -- elbrus-{4c,8c,1cp} --
but these aren't needed anymore), but there are no
std-def/un-def kernels or provides available.
There's more to it, but lacking a kernel is critical.

Maybe other arches might do similar things when needed,
or maybe this gets reverted in favour of a more generic
approach; but patching all starterkits or messing with
p9.mk per-arch (while leaving out regular builds or
any other image that might just build) looks worse.

...at least so far.

A few remaining tidbits lingering in RELENG-e2k-workstation.

This commit is actually a rework of what's been done
in RELENG-e2k-workstation private branch (along with
a few more generic fixups).

This started as a three-seater 801-PC support for
ALT Education 9.0 for Elbrus.

...and leave the choice up to runtime scripts and the user.

This is required on e2k, please tell if it hurts.

This is required on e2k (regardless of DE), please tell if it hurts.

Wonder if installer-feature-quota-stage2 was a problem
on other arches but having it in LIVE_PACKAGES fails
image build for me:

  livecd-installer-features: Conflicts: installer-common-stage2

and having it INSTALL2_PACKAGES results in another startup
problem (seems like quotas try to start a bit too early);
not that this one is a blocker but spoils the party nevertheless.

NB: relevant package versions are the same.

Also avoid workstation/extras pkglist: it's strongly hardwired,
seems like last-minute implementation :-/

These have been added to the image description
that was x86-specific initially -- we're lucky
that ARM-related bits are quite minor here but
let's keep the mixin away for the sake of e2k
for now: it's built in a different enough way
at the moment.

xorg-drv-mga2 is MCST Graphics Array driver for 2D part
of videochip found in Elbrus-1C+ APU (also to be a part
of Elbrus-2C3).

xorg-drv-smi is another fork of xorg-drv-siliconmotion
that's absent in p9/sisyphus; *might* be of some interest
to mipsel folks (they've got yet another fork it seems).

Ah, and do not override targets on e2k.

button.ko isn't compiled within elbrus kernel (or used in any way).

Done differently, no "button/power" event at the moment.

(turns off upon boot)

Some packages are still not available on some arches yet;
this time it's a e2k starterkits related fixup.

(still preferring 80-char wide xterm for proofreading)

...so that these can be handled by the feature.

Have to refer to MCST instead at the moment.

Make sure acpid will be running as acpid-events-e2k relies on it
(and power button handling relies on this one).

NB: need to do that before 10-services.

There's just no need to keep Windows-style local clock in RTC
on Elbrus.

ALT p9_e2k starterkits have turned this one up either...

Belongs to live as well now since we've got starterkits;
hopefully PDK publication project is done soonish
so we can just be back to normal.

This commit is packing a bunch of changes that went
into RELENG-e2k-workstation during its forked
development; it covers three distinct things:

- boot.conf preparation for firmware to load the image;
- fixup of packages common for e2k images;
- major cleanup of obsolete/unused cruft
  (unified kernel and reliable xorg autodetection
  allow us to move away from canned machine-specific
  configurations for the most part).

installer-feature-setup-plymouth needed make-initrd-plymouth.
make-initrd-plymouth missing for not X86 Arches in alt-server.
This resulted in a make-initrd error when installing on non-X86 Arches.

For check all targets.

Also drop use/build-vm, not needed.

Example:
@$(call set,GRUB_DEFAULT,uefi-firmware)
@$(call xport,GRUB_DEFAULT)

See features.in/grub/cfg.in/*.cfg

Example:
@$(call set,SYSLINUX_DEFAULT,harddisk)
@$(call xport,SYSLINUX_DEFAULT)

See features.in/syslinux/cfg.in/*.cfg