This has been basically asked for in this forum thread:
http://forum.altlinux.org/index.php?topic=36122

Thanks shaba@ and pauli@ for advice and testing.

This one is intermediate for openstack server too.

This one is a point halfway through use/server/mini
for an openstack server image; made the server-base
pkglist selection more explicit while at that.

This list has been borrowed from m-p-d's use.mk.in either
and adapted accordingly.

These have been imported from m-p-d, thanks boyarsh@:

http://git.altlinux.org/people/boyarsh/packages/?p=mkimage-profiles-desktop.git;a=commitdiff;h=ee6f940f6b543cd03e43dbabe66332654cd6f896

...and reworked a bit:
* tree -> flat for representation;
* flat -> tree for implementation.

Another zerg@'s surprise was the change with amarok,
k3b and ktorrent packages in sisyphus/p8: these have
been changed to use kde4libs/kf5 and KDE3-related
packages have now been renamed to kde3-*.

Handling this without metapackages is more tricky
so do just that.

This script was completely careless regarding the chance
to meet an empty variable resulting in plain "rpm -qa"
and subsequent attempt to, well, remove *all* packages.

Thanks zerg@ for being persistent this time, even if
he could probably find the culprit and send in this patch.
:)

- nvidia/nouveau rehash
- overlayfs support (lakostis@)

The problem at hand was that use/x11/xorg has been final,
and zerg@ just couldn't switch from nouveau to nvidia
when kdesktop needs that one.

Initial approach included a "big" FREE/PROP switch that
chose the particular KMODULES/PACKAGES to get added to
THE_* but that fails to achieve e.g. nvidia+radeon combo;
looks like these need individual switches.

Current lxsession would offer to lock screen but will silently
fail within default regular-lxde.iso environment (that does lack
any kind of X screen lock utility); add some.

This is a nice utility clamping default power strain
*and* heat generation on intel-based PCs; I was actually
surprised to see it available but not firing off at system
startup time; fix that.

stage2 only allows to run certain scripts and install packages, but
sometimes one need just to copy something to stage2 (like stage1 does).

How to use:

put files under ./files directory with the same structure as on
resulting image.

If aufs not available/broken we could try to use overlayfs.
NB: changes below doesn't work without modified make-initrd-propagator!

See also https://bugzilla.altlinux.org/32040
(there's no P:/O: in the new one so the update
must be done in sync here)

The use case at hand was: "we'd better backup this system
to a flashdrive before installing" (given quad-core CPU
and half-terabyte HDD); pxz is pretty tiny, no worries.

Looks like `alsactl init' needs this now:

http://forum.altlinux.org/index.php?topic=36177.msg285840#msg285840
http://bugzilla.altlinux.org/show_bug.cgi?id=32065

The problem is the same as the recent one with server:
FBDEV won't work for no good reason :-/

- starterkits-20160429

There were two problems:
- the latest pgsql related groups made installation
  impossible (yes, that last minute change);
- hardware testing shows that use/stage2/kms is now
  requisite as xorg-drv-fbdev might just refuse to work
  with what looks like a perfectly good framebuffer...

Do away with them *quick*.

Basically an updated p7.mk.

PostgreSQL has been long neglected way too bad in mkimage-profiles
and the actual builds, let's go and fix that!

Pg 9.5 is the current stable version
while 9.4-1C is the current version
patched to run 1C Enterprise.

This starts a sort of "server merger" by consuming
both samba4 and hyperv subflavours into checkboxes.

Rationale is pretty clear: environment -- including
hypervisors -- is just an install/run-time variable,
and the set of initial services is another one;
no need to maintain a distinct image for each value
when we've done enough of that to know we can merge.

These are based on regular-server-hyperv
(thanks Matt Lewandowsky yet again) turned
into a mere checkbox.

This is a clone of tagged/server+sambaDC pkglist
with added metadata *and* an installer feature
to make things happen at install time; not sure
if regular-server-samba4 is going away any time
soon though as it's useful standalone too.

"Failsafe install" disabling APIC/LAPIC looks somewhat obsolete
by now; the only reasonable part seems to be the attempt to force
VESA videodriver for the installer (should be done within installer
itself though).

Turns out that commit fb4bd77f broke two of the regular builds
by crippling their ability to reboot/poweroff via desktop menu:
http://lists.altlinux.org/pipermail/devel/2016-April/201319.html

Note that kde4 one doesn't need CK indeed.

zerg@ tells that Obsoletes: is flakey in fonts-ttf-droid
so it's better to specify these three packages instead.

- preparing for p8 starterkits

This single-byte error has led to premature variable
substitution thus non-existant "docs-" package being
requested; ouch.

live-privacy haven't graduated from beta status yet
but it's useful anyways; a bit of housekeeping
is due though.

gst-plugins-* was an /extremely/ bad and ugly idea indeed;
it pulled in every -devel it could.

This is to avoid "unzip.zip" situations with some NICs:
those needing extended firmware package (which is hefty)
can at least install it by hand off the ISO.

*Maybe* a switch to use/firmware will appear reasonable
some day for this image either, don't know yet; this adds
firmware to installer itself (should only be needed if the
storage device used for rootfs *needs* firmware found in
that package as networking setup is omitted from JeOS
installer).

Rationale: it's the minimalistic image for those who know
what they're doing, let's maximize their chances to get it
installed and running by using a recent kernel.

My failure to recognize that it is a "generic" server that
might need some generalization and not an already specialized
one like OpenVZ HN installer had to be fixed up some day;
today is fine.

Basically, let's move package groups ("checkboxes") and alterator
from server-ovz to server, and maybe beef it up a lil' bit more
later; server-ovz is still far from jeos-ovz but the difference
that looks unmergeable is strict sshd control setup that's going
to bite those unsuspecting, so let's leave it for those of us
who are more suspicious of stray ISOs. :)

Services and tools are clearly different entities,
and we need tools for a slimmer OpenVZ HN installer.