+installer should work everywhere it can at all,
but full-blown one is currently developed on x86;
provide at least the reasonable chunk elsewhere.

It can be useful for bcache repair.

Show system-config-printer in the alterator.

https://bugzilla.altlinux.org/34217

See https://lists.debian.org/debian-devel/2017/06/msg00308.html

ALT bug #34142.

It usefull if something goes wrong in the alterator-vm.

Seems some other branding-*-release can be installed in live
chroot and post of needed branding-*-release package don't copy
these files.

One browser will be enough. Let it be firefox.

For touchpad during installation.

Otherwise they can be pulled on live.

This is more appropriate default value nowaday.

If set then don't remove apt and rpm from live images.

Use it in the image filename, so we'll know what version of a distro
it is.

The 'lang' option will be added by gfxboot according with
choosed language.

If service already listed in the config files, then ignore
status in the profiles variables.

- ldm feature (lakostis@)

Added glvnd packages to test.

Linux Driver Management (aka LDM) allows easy configuration of different
hardware. Currently this hook does GPU configuration on systems with
multiple GPUs (aka Optimus/PRIME).

...as gtk one is quite bare to be frank.

Looks better than lightdm-gtk-greeter indeed;
present in both sisyphus and p8 as of today.

This adds mkfs.fat and fsck.fat utilities to installer
so it's able to create/mount this "filesystem" as well.

- e2k & profiles

The comment was incomplete since commit
1f13b3a0.

See commit 2d257a42
for details, this just brings those to pkg.in/profiles/
(along with the generic archdep support, of course).

...to reduce the divergence with the rest of related variables;
these installer profiles affect the default checkbox states.

101's one has been useful enough so far.

...which will only result in a FAILED message,
most probably the solitary one throughout the
whole sysvinit boot.

The goal was simple: every use/e2k/{x11,install2}/$MACHINE
must be self-sufficient regarding platform support, that is
it must depend on the corresponding CPU-specific target.

A bit less make-tech but still better overall.

NB: llvm cleanup is not needed anymore after upgrade to
    Mesa-17/llvm-3.7, should be dropped like this year.