The main challenge for this change appeared to be lightdm:
it can do dualseat but in a quite peculiar way tied to systemd;
while wdm-based implementation well prepared and described by viy@
can survive both systemd and sysvinit just fine.

branding-alt-workstation-mate-settings pulls in lightdm-gtk-greeter,
and lightdm takes over; it should probably be masked in systemd case
(sysvinit should need no further hassle as /etc/X11/prefdm considers
wdm before lightdm for historical reasons; or /etc/sysconfig/desktop
could be filled in to be sure) *but* the current stopgap "solution"
is what it is now.

See-also: http://altlinux.org/X11/DualSeat

These describe what's needed to set up a single-seat (as usual,
now just default) or dual-seat (out-of-box, given a checkbox)
Elbrus 801-PC.

Huge thanks to bircoph@ for actually implementing this!

...for now as

  xdg-su -c "/usr/sbin/synaptic --update-at-startup \
    --dist-upgrade-mode --non-interactive"

got me exit code 4.

I decided to switch lightdm greeter from gtk to slick,
while adding the default user created to xgrp group
(to facilitate them access to DRI device nodes)
and turning off MATE's desire to spend extra resources
on bells and whistles though compositing window manager.

Elbrus 101-PC was initially supported through kernel
modesetting driver only, now it's got a sort of native
driver running on ALT too.

IIRC it's actually looked for by EVMS fat plugin.

...actually just not published for e2k yet;
avoid uncommenting the lines in sources.list.

This is to make building addon images possible;
those carrying packages but lacking any stage2.

doc/archdep.txt was the reason to look closer,
and some other files needed a bit of facelift
by now too (would be better to do that in sync).

There's an ISO9660 COPY tag for license info file;
make use of it, factoring use/docs/license out
while at that.

One of the goals was to make it hold the reference
to reference to GPL in regular builds and starterkits
;-)

A bunch of duplicated variable names for mkimage,
just short-circuit those to the already available
(and hopefully filled in) BOOT_* ones.

Every .iso was assumed to be bootable since the very beginning[*],
and isoboot images were deemed to be x86 isolinux ones; this didn't
change with basic ppc/armh support as I never ran into hardware
that would _boot_ those ISOs, not only run the code, and it was
only e2k isodata project that finally forced this refactoring.

It's still not perfect: pack and syslinux features still end up
somewhat interwoven, and too much places care for architecture
the image is being built for (instead of archdep features tossing
their appropriate bits and pieces in).

Should help:
- any-arch regarding isodata images;
- {x86,aarch64}/efi by decoupling isoboot and isolinux;
- ppc{,64} as introducing yaboot support will be easier now;
- mipsel{,64} too, hopefully.

* I knew of school addon images baked with mkimage-profiles-desktop
  but postponed and then neglected the whole problem for years...

This one will be handled by MCST at the moment.

- alt-workstation: x86 (sem@), e2k (me)

It's no more in p8 and sisyphus.

It's the common part that should be more or less architecture
independent (given enough packages in the corresponding repo)
that's been moved into a mixin; archdep bits kept in basealt.mk
(albeit rewritten).

Note that this approach should help building ALT Workstation
for both new arches (like aarch64 or mipsel) and new targets
(like vm) altogether.

...to those arches having it.

...to make those usable on other architectures as well!

+vmguest should work everywhere it can at all either;
it's most advanced on x86_64 in terms of hypervisors
available; still aarch64 has kvm too.

+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.