Forward-port of b84182c5cb684afbd30ed1f9e5b6f89f55b4b53f
commit extended to handle /boot as well.

This time it autostarts using livecd-fgfs and primus
if possible; firefox and GUI mixer are the notable loss
but the clarity of "boot into FlightGear" should sort of
compensate for that.

Ah, and Tu-154 by default.

That reflects the packaging and distribution practice
having formed during last year or so...

Looks like Qt4-based imagewriter fits these images better
than Qt5-based rosa-imagewriter; so be it.

Some of the wares wouldn't actually work on closer examination,
better leave these out for now.

Some apps won't start and some don't have any visible effect.
Let's postpone these.

plasma-applet-networkmanager is suddenly no more in Sisyphus,
had to replace with kde4-plasma-nm and force gtk applet away.

Some of the packages have been identified as abandoned
and were purged; some of those with problems have been
reportedly fixed since.

See also:
http://altlinux.org/?title=Talk:GNUstep/Applications&diff=28911&oldid=28730

Current Sisyphus' xorg-drv-intel works somewhat better
with recent kernel drivers on my HD4000 GPU, and icewm
is not compositing at all; providing another test/backup
image fitted with newer kernel should do no harm.

Thanks real@ and kostyalamer for packaging these
along with new and shiny menufiles; a new pkglist
seems reasonable by now.

This package has been built and recommended by cas@;
it requires Qt5 which hasn't been needed for anything else
included in regular builds so far so let's extend kde4 one
to begin with.

For lewellyn@freenode and his Hyper-V Generation 2 VM,
regular-rescue happens to boot there.

lightdm isn't going to turn off the system properly
with no systemd-logind around ("for no good reason",
that is); good ol' wdm for installed system and the
similarly ol' autologin just work though.

nodm is not gonna cut it since user PATH is weird
within the session breaking livecd-install by putting
/usr/sbin before /usr/bin while it shouldn't be there
in the first place.

Looks like nodm doesn't reset the PATH set within
/etc/rc.d/init.d/functions which results in sbin
path components hitting user's PATH; livecd-install
which uses consolehelper was what broke first for me.

And this link should illustrate some of the problems
tackled by this kind of scripts...

Servers can POST much longer so having to play hide and seek
with a boot menu isn't going to be exactly entertaining;
let's bump the delay to something comparable at least.

Thanks hiddenman@ for mentioning the obvious-but-unnoticed.

Don't remember why this hasn't been there already;
looks like a worthwile addition though.

As it happens regular-rc testing has shown that cinnamon,
gnome3 and kde4 flavours included NM via their pkglists
and dependencies (which used to result in live feature
enabling NetworkManager service wholesale when found);
now when handling default services has become more strict
it became apparent that these images have got their LiveCD
mode running without network by default (installation does
set that up though).

It looks like an easy way to just stick +nm into .regular-desktop
dependencies but then razorqt, sugar, xmonad would get NM which
is not what they're gonna handle; e17/e18 too.

- don't insist on k-m-r8168
- codebase deduplication

This has to be present with default RPM macros, otherwise:

  rpmdb: /home/altlinux/tmp: No such file or directory
  rpmdb: unable to create temporary backing file

See also http://bugzilla.altlinux.org/26514

We don't really want to disable NFS portmapper completely
but having some extra root code listening to the world is
really unneccessary unless explicitly required.

Applying "control rpcbind local", thanks ldv@ for advice.

50-setup-network was a hasty hack (surprise!) that used to do
what net and net-eth features have been created to do since;
just drop the duplicated crufty code.

Unconditional resolver setup isn't done now: those with static
setup are better off doing it explicitly, and those with DHCP
should be fine already.

NB: /etc/hosts *is* fine within setup package *but* hasher will
    overwrite it with a copy of host's one; let's reset contents
    to initial at least until hasher gets fixed and the fix is
    rather deployed in the wild.

03-services was a hasty hack that has been long done properly
elsewhere, namely in a specialized feature; finally got around
to deduplicate it out.

There was an extra DISABLED=no line written to interface configurarion
that's been superceded by the subsequently added parametrized one;
just drop it.

Thanks glebfm@ for spotting the garbage.

Well actually it shouldn't -- except for rEFInd the boot manager:
branding graphics within the build environment are used to add
a single background image to EFI/refind/icons/ thus the change.

Wonder how this got lost though as this screenshot:
http://en.altlinux.org/File:Altlinux-rescue-uefi-memtest86.jpg
clearly illustrates it was working back in December indeed!

It conflicts with r8169.ko inobviously.

The whole mess looks like this:
- r8169.ko doesn't work for all of Realtek 8111/8168/8169 mutations
- r8168.ko works with some of the chips r8169.ko doesn't
- r8168.ko also works with many chips r8169.ko works with
- r8169.ko is provided by kernel-image package (thus default)
- r8168.ko is provided by kernel-modules-r8168 package (optional)
- kernel-modules-r8168 package requires r8168-blacklist package
- r8168-blacklist package is a one-liner that blacklists r8169.ko
- STAGE1_KMODULES wouldn't include r8168 (std-def) or rtl8168 (led-ws)
- sub.in/stage1/modules would mention r8168.ko (m-p-d: r8169.ko)

So a LiveCD built with use/kernel/net might work with RTL8111/8110
just fine when booted live but fail to automatically load the module
when installed onto hard drive; manual modprobe r8169 would work though.
NB: some of the chips (those available to me) would work just fine
both ways -- this has contributed to fixing this *that* late.

Bottom line:

  do not install backup/kludge drivers overriding main ones by default!

Thanks sem@ for providing the crucial hint.

This is about (a)synchronous package builder in fact.

- docs week
- deflogin: empty ROOTPW explicitly ignored (potential security fix)

That's how it evaded the rescue part of regular-sysv-tde.

Looking as how every .regular-sysv-gtk descendant ended up using
use/syslinux/ui/gfxboot by now it seems better to just stick it there.

use/deflogin will result in ROOTPW being exported no matter
is it set or not; xport() can't check before exporting as it
relies on lazy evaluation when the actual ROOTPW value can be
set or modified after exporting GLOBAL_ROOTPW for mkimage.

So let's not even pretent we can differ unset ROOTPW from
empty ROOTPW: both result in empty GLOBAL_ROOTPW as of today.

Fixing this would require moving the exports into a separate
makefile being included after all the configuration and checking
each variable for being defined before exporting the corresponding
GLOBAL_ prefixed one.

Yes this might be a security fix in some cases.

It's preliminary but rather working by now;
one of the main woes is #29497 so far.

xterm has been overduplicated,
moved to pkglists for clarity.

TDE images are pretty modest regarding resource consumption
thus suitable for older hardware; a slower flash drive can
stall indefinitely showing slideshow and not going any further
with actual package installation so let's put a cap on that.

Added use/branding/slideshow/once as one of the uses
albeit the interface is universal; see this page for
more info: http://altlinux.org/branding/slideshow [ru]

The service and initscript have "connmand" name
while the package is called "connman" indeed.

Shame on me; this became apparent
while building regular-e18-sysv.

Speccyfighter asked for NTP support within sysv-tde flavour;
meant openntpd apparently, fixing up.

gnustep-AddressManager has been replaced
with gnustep-Etoile-AddressManager, ditto
gnustep-DictionaryReader; see also [ru]:

http://altlinux.org/?title=GNUstep%2FApplications&action=historysubmit&diff=28795&oldid=28694

Defining a one-time variable is useless in this case,
and README should state the undefined ROOTPW status
explicitly (since it's now as advertized, heh).

The goals listed are pretty important to have them ordered
by priority; collaboration is definitely more important
than dynamic range of release managers' experience.