propagator-20150306-alt1 and make-initrd-propagator-0.25-alt1
have made it actually possible to use resulting LiveCD images
along with USB flash media to achieve data persistence that's
been long available for BIOS boot mode (see also #28289).

This isn't perfect but let's try flipping the switch:
all desktop regular builds are now "live_rw" by default
in EFI mode.

This requires mkimage >= 0.2.17.

This image doesn't deign to waste one's time by presenting
them with a bootloader menu and a few other things;
make it even less verbose where not neccessary.

Looks like we'd better provide a few really good console fonts.

cool-retro-term 1.0.0 exhibits a bug without these fonts around:
glyphs would be drawn higher than cursor with upper half being
cut off (found out by putting my current crop of font packages
into livecd environment and removing them until the correct
behaviour would get broken).

xpra.org and winswitch.org are wonderful applications
helping one working with X11 apps all over the place,
running those on local and remote desktops and servers
with persistent sessions.

These aren't exactly trivial to plan and use but icewm
isn't for newbies either; thus these seem like nice match
for an "X11 thin client" image.

Size addition is ca. 50 Mb as of today which is a lot
but worth it.

This nice FTP/HTTP client has one issue that bars its inclusion
into every regular desktop image: lftp.desktop file that pops up
in menu but only offers an xterm with a CLI-based utility which
feels embarrassing for a casual user unfamiliar with its power.

IceWM users shouldn't be surprised however.

...as suggested by Sluggard again:
http://www.opennet.ru/openforum/vsluhforumID3/101671.html#143

This has been suggested by Sluggard at opennet:
http://www.opennet.ru/openforum/vsluhforumID3/101671.html#91

It's been missing roughly from the start there :-/

The former approach to handling "LiveCD with sessions"
has been to mangle "automatic=method:cdrom" into
"automatic=method:disk,label:ALT*" within gfxboot
so that propagator and make-initrd-propagator would
try and discover/create a filesystem labelled
"alt-live-storage" on a LiveFlash's free space.

Then "live_rw" handling has been unified in
make-initrd-propagator (as of 0.18-alt1) to accept
any of "label" subparameter or "live_rw" argument
to go and create_disk_slice().

Then propagator's cdrom.c has been fixed to actually
try sdX1 before sdX (as of 20150306-alt1).

And now it's all been tested to verify that:
- flash "ro" and "rw" boot is OK
- CD-ROM "ro" boot is OK
- CD-ROM "rw" boot is fine given that there's
  a partition labeled "alt-live-storage" elsewhere

This is a can of worms indeed :-/

References
~~~~~~~~~~
* http://altlinux.org/initrd-propagator
* http://altlinux.org/make-initrd-propagator
* http://bugzilla.altlinux.org/28289

The problem is URW again (just as in commit ab44f800),
and the workaround is the same either.

That's what's been found via "qt game" query with Synaptic
while running a functional testing session upon lxqt starterkit
beta as of 20150305 :)

It's entirely unclear to an unsuspecting curious user
where the actual results of a proposed example hasher
build end up; that's ~/hasher/repo, just state that.

Is it news or was it missing all the way through?..

The former install2-only "bloated binary" purge script
happened to hit stage2 (which is a lot more than just
install2); a kind of safety net has been stuck into it
to guard installable LiveCDs against this particular
cleanup but seems it was not enought for ildar@ who
reported this problem almost three years after it was
introduced.

This change re-places the script back into install2
section; the binaries in question amount for ca. 8 Mb
(except openssl ildar@ asked about); if these are deemed
unneccessary within any other stage2-based subprofiles,
please step up with details.

- vmguest, install2: refactoring

use/vmguest/vbox/base used to pull in DRM modules
which are required for vboxvideo but useless without
xorg bits; and all of these aren't needed in jeos.

Things might break, doublecheck please.

It's half a megabyte but useful enough.

It's a bit sad to hit a minimalistic environment
with apt knowing no repositories at all...

use/cleanup/x11 has been extended with commit 122c305b,
a few manually specified items can be dropped now.

This nice utility is preconfigured for network monitoring
in default icewm configuration but was missing, unfortunately;
just fix this.

When installer-feature-systemd-stage3 hits BASE_PACKAGES
it pulls install2-init-functions in which is wrong
(one of the consequences is that alterator-browser-qt
lands into even a very basic server installation).

And install2 doesn't even need that package as init feature
carries a script hook that does the same...

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

This project has evolved/merged into LXQt which has been
packaged for both p7/t7 and sisyphus by now, no need to
carry on deprecated bits.

NB: 0.6.x still have it as t6/p6 still bear razorqt.

...the one actually meant for regular builds.

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.