Both might be useful in some context but serve no real need
given the installer one, at least this year.

This rotten cherry-picking is ridiculous of course
but that's the price to pay for hard dependencies...

These aren't going to be really needed in that environment,
please refer to the more complete environments like rescue,
live, or an installed system.

xterm is pulled in by xinitrc (as xvt),
xdg-utils by alterator-browser-qt (for xdg-open).

...or are fine with fbdev like in case of installers,
especially minimalistic ones.

My gut feeling is that we're not going to see glib2's
messages a lot within installer environment anyways.

And there's a forgotten /usr/share/X11/locale/ too.

These are required by no package after the intermediate
cleanup has finished.  Argh.

Installer doesn't do systemd and needs no service files.

An installer needs video playback acceleration
when it has some content to show and some means to;
as long as these are not supported just drop this
unconditionally.

server-nano is intended to be slim; it doesn't need VNC
installation support and provides no LUKS tools either.

These are only needed for alterator-vm when making
LUKS encrypted partitions; ideally the extra libraries
would be omitted automatically when luks isn't included.

At least don't purge it with no questions answered.
Thanks naf@ for posting #29901.

The mixin concept and name has been borrowed from Ruby
language -- it's a kind of thing that can be added to
more or less whatever suitable; the problem it tries
to solve is that incrementally building up the image
configuration breaks when one would like to change
something that's been configured in early enough so that
grafting early will warrant a lot of duplication later on
but inheriting too much things that need to be changed
gets too much hackery in.

It started while trying to build an installer image
using configuration bits and pieces collected while
bringing an installable LiveCD together: there are
just too many livecdish things in a LiveCD to try
and rebase the actual desktop configuration things
onto an installer, so putting these into a mixin
to be reused within both livecd and installer
seems the way to go.

Looks like today's xorg won't autoload radeon_drv but
insists on ati_drv falling back to fbdev if it's not there;
FlightGear runs definitely slow on C-60 APU with that.

I didn't specify ati since it pulls r128 and mach64 modules in
which are rather useless in this context (accelerated 3D graphics).

Burn.app won't list a USB DVDRW drive with CD-RW inside
(NOT_FOUND), and its README states explicitly that wodim
is not supported yet.

Mixer.app would start with three knobs none of which would
actually change any mixer channel.

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!