- p8+

mixin/e2k-desktop was asking for separation from its day zero,
and the rest just came in naturally (the temporary patch to
add lxqt and mate looked awfully with all the duplication in).

This is to make desktop+lxqt packages installable on e2k
as there's no qt4 package within this Sisyphus port and
things might just stay this way (it's long unsupported,
looks like porting software to qt5 is more worthwile
an effort).

There's one more removal though: qupzilla. This browser
fits lxqt like a glove *but* it's pulled in already by
mixin/regular-lxqt, and browser feature is available now
to make the selection more flexible.  It's also going to
be renamed on the way to incusion into KDE SC.

...for firmware-rt61pci; thanks to an anonymous bugreporter.

See-also: http://www.opennet.ru/openforum/vsluhforumID3/112310.html#177

There was a semi-awful lot of long-abandoned targets
spotted while factoring out mixins; let's just drop
these for good, and if anyone needs some of those
drop me a commit.

These branches are officially unsupported for the whole
two years, probably just the time to clean up.

See-also: http://altlinux.org/branches

These have appeared in desktop.mk, regular.mk, vm.mk
over time, and there are two problems around.

The minor one is that mixins have been introduced as
handy reusable bits close in context of their use;
this practically means that they fall under the same
class restrictions as their parent targets, that is
a mixin coming from regular.mk will only be available
for "distro" IMAGE_CLASS, and so on.

The major one is probably the worst design flaw in m-p:
building images from ground up, where ground is a valid
standalone buildable target as well.

Life has shown that we rather want to build up images
the other way around, choosing what essentials go in first
and then fitting the fine details along with the packaging.

The first sign of this difference appeared with ARMv7 Simply:
we had a well-built configuration aiming for x86 ISO, still
we needed roughly the same app/environment configuration
put into armh disk image.

Those platforms were different enough that we didn't actually
plan shipping *lots* of distributions but the problem was clear,
and it was much alike to the one that sprang m-p to life in the
first place (when we had a range of "common" distros and needed
to create and maintain a set of "school" ones that mostly had
similar or even identical difference to their respective base
ones -- and we couldn't do something like conf.d/p8.mk does now).

So mixins are going to become the softer way to turn m-p's
target configuration chain upside down to considerable extent:
build up what you're going to mix into the various deliverables,
and make it as portable across image classes, hardware platforms,
repository branches as feasible so that total maintenance effort
needed goes down or at least doesn't spike too bad.

And here's the first strike at that.

This one has been clearly duplicated before.

It's been expelled from sisyphus.

See-also: http://git.altlinux.org/tasks/archive/done/_183/187993/

- regular-engineering

...instead of xfce4-mixer which is based on gstreamer 0.10
(with its mixer API that perished in 1.0); this has been
tested on e2k already.
Suggested-by: Mikhail Efremov <sem@altlinux.org>
See-also: http://forum.altlinux.org/index.php?topic=36177.msg316175#msg316175

Weird it got overlooked in the first place.

ROSA's legacy...

Suggested-by: Speccyfighter
See-also: http://forum.altlinux.org/index.php?topic=39476.msg315597#msg315597

Suggested-by: squire
See-also: http://forum.altlinux.org/index.php?topic=38966.msg312602#msg312602

Suggested-by: Evgenii Terechkov <evg@altlinux.org>

- seven years ago...

...and somewhat improve vm/e2k-xfce.

Radeon HDMI as the default soundcard isn't really optimal,
and trying to push 44100 kHz samples towards 48 kHz interface
isn't going to sound great; provide sane ALSA dmix defaults
for Elbrus-401 PC workstation.

BASE_PACKAGES_REGEXP and THE_PACKAGES_REGEXP,
to be exact; the lack of handling these appears
to have been the culprit of firefox missing in
vm images which use/browser/firefox.

This reverts commit 41a3f091:
at least build-vm doesn't do *_REGEXP (which is worth fixing
but all relevant branches got firefox-classic_theme_restorer
so this tweak is now irrelevant and a bit wasteful).

...and leave it for possible further investigation
only if debug level is 2 or higher (which is uncommon).

It's strange but ve/builder and distro/live-builder
along with distro/regular-builder are all mostly
"independent", that is duplicating functionality
without any reasonable gain; spotted finally.

Suggested-by: gremlin@altlinux.org

- e2k

Weird but the last round of image builds on e2k started complaining:

  Makefile:95: *** target file `debug' has both : and :: entries.  Stop.

Looks like these should have been fixed indeed.
But why didn't this surface before then?

Let's build an Xfce based image, got anything needed (well, almost:
xorg-drv-libinput isn't there and no one is crying over that here).

And let's change "e2k" suffix to be prefix while at that.

BR: imsettings -> libgxim -> ruby, and it's missing still.

The early builds used to rely upon a non-committed
rootfs/files/etc/X11/xorg.conf within this feature
which was a bit annoying and would have screwed an
Elbrus system based on any other GPU.

So let's provide some flexibility by packaging it.

Turns out that vm images might need localization too,
not just live ones.

The current state made vm images belong to root group,
no reason to not change those to the primary group of
the user building an image.

kpartx -d -s could fail in some circumstances,
make a safety cleanup call more verbose.

These used to carry (or need) their own means for the same
problem of extra services consuming bootup time.