The gnome3-regular one adds quite a few megabytes,
let's keep the mid-sized -default for common targets
while moving -regular to, well, regular one.

This has been asked for by shaba@:
http://lists.altlinux.org/pipermail/devel/2015-February/199506.html

The installer feature added is a trivial wrapper around
apt-cache nodeps to uninstall the ^lib packages that have
no more dependencies upon those when the temporarily
installed packages like alterator-browser-qt get removed.

Specifically for the minimalistic systemd-based server image
suggested by shaba@.

This has been simply use/net but it looks like we've got
some people who would like to cope without etcnet, even:
http://lists.altlinux.org/pipermail/devel/2015-February/199506.html

Adjust its usage accordingly.

This has only been useful for plymouth feature,
and +installer shortcut included this target
for all the wrong reasons as it seems today
(thus blocking the DRM-free server installers,
for example).

This one enables a spare shell on tty9 just in case.

- regular rebase

This doesn't look like a clean solution, whitelist should be
way more reasonable; still better than dirty builddir though.

...unless we're debuggin'.

Base vagrant-compatible disk image seems good enough
to have a try at building some public stable sample...

The resulting image size will be less than the specified maximal one
as it's thin-provided with contents taking up what they do.

This authorized_keys file has been downloaded to get incorporated
into a script hook but was looking common enough to be forgotten
during pre-commit feature cleanup unfortunately; fix that.

How did it manage to evade pkglists so far?
These are very useful:

apt-cache list-extras
apt-cache list-nodeps

A few more leftover libraries tend to hang around after
purging extra alterator packages that have fired already
during installation stage3; this change might hurt someone,
please do notify if that is the case (OTOH one isn't forced
to use it or to inherit intermediate targets that do so).

The issue at hand is that some sneaky stage3 alterator modules
seem to have tossed alterator-browser-qt (thus libqt4* and friends)
into base server installations; while this must be solved in within
package base and should be worked around by server feature probably
let's start out with leaf targets.

epiphany (or fontconfig?) insists on URW fonts for rendering
webpages like http://opennet.ru which hurts my eyes; looks like
/etc/fonts/conf.d/60-alt-post-user.conf would override these
with e.g. Liberation or Dejavu (with the latter being inferior
to the former, IMHO).

...so that regular builds really have common ground again,
which is something that got broken with regular-jeos introduction;
adjusted jeos and builder flavours to make use of this.

...so base is base and bare is freed for a leaner entity...

There's considerable confusion accumulated over the
expansion of regular builds with non-GUI targets:

- bare meant quite a lot including wireless;
- base meant GUI base actually,

so rescue, server, and especially jeos images had to
either cope with the bloat or start from scratch.

Let's fix "base" first...

Looks like QEMU 2.2.0 gets surprised with some kernel module
that udev tries to load during "Populating /dev:" boot stage;
dropping *both* +vmguest and +wireless dependencies does help
while switching to un-def kernel flavour doesn't (as is or with
any single one of these two deps removed).

Thanks user who reported the problem at opennet.ru
(alias "myhand").

- vagrant feature (closes: #28553)

This should be built as vagrant-base.vdi (xz before publishing).

This feature adds initial vagrant-compatible box
build support as outlined in #28553.

Looks like there's a race condition somewhere: this script
will fail to clean up after itself when considerable background
load is inflicted upon the host it's running on (e.g. LA ~16
on a 8-core, single-disk system).

Note that this commit is NOT enough to win that race
but just a step in the right direction...

It's unwise to skip the common storage driver,
and vagrant (which uses virtualbox by default)
is likely to crash and burn as well.

This has been suggested by cas@ and sounds quite reasonable
given that we ship rsync anyways.

altlinux-p7-kde4-20141212 images had a problem:

- the generic starterkit profile is tuned
  for modest disk space consumption;
- KDE4 is quite extensive;
- kde4-regular subpackage tosses in most of KDE4 SC

...thus the livecd wouldn't autopartition enough
space for root filesystem when being installed.

volumes-profile-lite specifies 10Gb rootfs currently
which is just fine (-kdesktop one starts with 30Gb),
let's use it until vm-profile management is imported
into mkimage-profiles or things are redone completely.

This feature operates LIVE_* variables specifically
(as opposed to the more generic THE_* ones) so +alsa
isn't exactly suitable but reusing the pkglist that's
just been factored out is fine.

Split package lists:

- base alsa packages (also needed in pulseaudio-based installations)
- additional alsa packages (needed only if not using pulseaudio)
- pulseaudio packages

- fix the lists copying fix

cp(1) would get confusing arguments with no files to copy
if there are no lists to handle; employ xargs(1) as promised
to handle this properly.

aris@ tells that it's been specified as totem dependency since,
no need to carry this temporary duplication on.

This might come handy for those who have to deal with iDevices.

- fix lilo check for vm images

The check introduced by commit d7689f30 while rewriting tar2vm
(which presumed x86) was subtly broken: it checked for *host*
binary before preparing *chroot* configuration file for it.

Wonder how many build servers run lilo over here that this BUG
has managed to evade attention for almost two years...