It looks like this package livecd-firefox is very outdated.

This feature complements the live image of the second stage with installation
image-specific settings and scripted hooks.

It is recommended to connect using +live-installer to ensure that a typical set
of installer-related features is included.

Unlike the install2 feature, a separate image of the second stage of 'altinst'
is not built, but the live image is supplemented with installer packages in
order to reduce the total volume of the iso image.

Installation consists of two stages:
1. The live image is unpacked, as in livecd-install
2. Install additional packages BASE_PACKAGES and package groups THE_GROUPS as in install2.

Unlike install2, only those packages that are not in the live image are placed in the main repository. This is how the size of the iso image is reduced.

livecd-run-hooks runs hooks from /image/live.hooks/ by default.

check conditions of  make  for equality of variables with an empty value
instead of check definition.
A defined but empty variable under all these conditions results errors.

Add the possibility to directly configure the desktop app
for livecd kiosk mode to start.

This should have been done as soon as livecd-runapp
hit the streets -- livecd-{0ad,fgfs} definitely must go
as adding a line into config is trivially done near
the only place that requires them (conf.d/live.mk).

TODO: might be more generally useful for vm/* too,
      take this out into a separate feature then.

Edited: https://lists.altlinux.org/pipermail/devel-distro/2022-September/002889.html

Chroot can be two or one, work or image.
Package lists of work chroot cannot take into account packages that
will be installed into it after run-scripts.

The proper form is "does not" here.

This is useless and even harmful for images that include both live
and install2.

Required by shaba@:
https://bugzilla.altlinux.org/show_bug.cgi?id=41588#c1

Made by analogy with features.in/repo/image-scripts.d/90-enable-repo.

/usr/sbin/install2-init-functions is provided by several packages.
Because of this, extra packages are installed. It is necessary to
simplify the task for the packages manager.

The commit 99695713 used this variable
even though it didn't exist yet. A good reason to add this variable.

make-initrd-propagator >= 0.44-alt1 always create alt-live-storage.

It is customary to set a variable without the GLOBAL_ prefix. It
is added to the name when exporting.

I made by analogy use/cleanup/live-no-cleanup-docs.

Since both targets have long names and are needed together,
i made use/live/no-cleanup.

Use target use/live/no-cleanup should be used instead of:

@$(call set, GLOBAL_LIVE_NO_CLEANUPDB, yes)

Not a given on any architecture...

There are two different versions of the script with the same
name for different subprofiles, sharing some of the same bugs
over the years, *sigh*.

Shoving those into stage2 would yield online repositories enabled
there too which *might* be wanted but will likely need installer
support (at least some better error handling, the current culprit
with unavailable repositories being apt-pkg's size estimation).

Fixes: d2f892ab
Fixes: 0f4ee98f

This reverts commit c70f18fc.

On hybrid images recorded on a USB flash drive, rather than a
compact disk, this menu item loads the USB flash drive itself.

Apparently we don't want it with systemd-logind.

crond is needed for log rotation.
See-also: https://forum.altlinux.org/index.php?topic=36177.msg346822#msg346822

Install /etc/*-release files if needed.
Reported-by: Ivan A. Melnikov <iv@altlinux.org>

...and drop duplication tossed in by i-f-online-repo.

See-also: https://bugzilla.altlinux.org/36952

Seems some other branding-*-release can be installed in live
chroot and post of needed branding-*-release package don't copy
these files.

The places of the terms *do* affect the sum in apt's case;
start with lowlevel items like SYSTEM_PACKAGES and end with
high-level ones like THE_LISTS to reduce the chance of getting
hit by premature virtual dependency expansion/fixation.

Adapt live and rescue features accordingly.

See-also: https://bugzilla.altlinux.org/show_bug.cgi?id=30806#c5Suggested-by: Leonid Krivoshein <klark@altlinux.org>

...explicitly; this has been triggered by the change to
livecd-install as of 0.9.10-alt2 (doesn't R: alterator-grub
anymore to allow non-grub platforms as well).

This should be a no-op _together_ with the mentioned change
by now as grub is selected explicitly; will take more attention
for e.g. e2k as the problem just shifted here from livecd-install.
Reported-by: Leonid Krivoshein <klark@altlinux.org>

These used to carry (or need) their own means for the same
problem of extra services consuming bootup time.

Another minor facelift:
- s/ALT Linux/ALT/gc (where applicable);
- s/7.0/8.0/g;
- 2017;
- e2k;
- links.

...instead of (often-crowded) ftp.altlinux.org for updates.

This is unfortunate but Sisyphus' Xfce can't really strive with its
default /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml,
namely IconThemeName; while p8's one still does pretty good.

Thanks antohami@ for his analysis and workaround suggestion.

See-also: https://bugzilla.altlinux.org/32924
See-also: https://lists.altlinux.org/pipermail/devel/2017-February/202348.htmlSuggested-by: Anton Midyukov <midyukov-anton@ya.ru>

See the previous commit for rationale.

It's been an old intent to add/move feature-specific
variable documentation into the features themselves,
this might be a pilot project. :-)

The reason behind this silly patch is that the default URL
can be left alone with no rebuilds neccessary but with the
intranet services delivered through a "captive portal" or
a redirecting proxy; we definitely don't want the canonical
wiki URL, http://www.altlinux.org, blocked by a rule made
for redirecting the default homepage, so let it be another
one which is served but not widely known or linked to.

This one is alike to install2's one; it's not a shared rootfs
script/variable though as contexts differ a lot, let's be careful.

The commit has been missing from 1.1.64 somehow, found in patch
series while figuring out why LIVE_CLEANUP_KDRIVERS seems to be
just ignored in live-privacy *after* the massive rebase of that
branch...