startup contains configs needed all.
e.g. /etc/sysconfig/i18n needed for /root/.i18n from package rootfiles-alt.
See also https://bugzilla.altlinux.org/43107

systemd-utils-standalone no available for p9.
apt-conf-ignore-systemd guarantees the installation of
systemd-utils-standalone.

This will solve the problems with the update (p9 -> p10).

systemd-settings-disable-dumpcore will soon be removed from Sisyphus and p10.

udevd-final needed for sysvinit with X11.
Otherwise, the system stops responding to input.

startup soon won't be installed by anyone.

This is necessary for kernels 5.10 and higher on systems with sysvinit,
since no one else on these systems except this service will mount
evivars in /sys/firmware/efi/efivars.

Also needed for livecd.

Use systemd-settings-enable-log-to-tty12 (included by +systemd-optimal)
instead.

This is necessary to prevent installing the systemd package on systems
with sysvinit.

Use polkit-sysvinit as a workaround.

See-also: https://lists.altlinux.org/pipermail/devel/2019-November/208963.html

Reverts: 08d93ed8
(and several slightly more involved places)

Conflicts with systemd-utils.

See-also: http://bugzilla.altlinux.org/37352

See-also:
http://git.altlinux.org/gears/s/systemd.git?p=systemd.git;a=commitdiff;h=30c28ce9e6d8d006c81b6bbecaf6423a08d8f3f5

Not all systemd-based images need these settings,
so don't change +systemd alias.

See-also: https://lists.altlinux.org/pipermail/devel-distro/2019-July/001710.html

ConsoleKit2 removed from Sisyphus
See-also: https://bugzilla.altlinux.org/37040

elogind is the systemd project's "logind" extracted out to be
a standalone service.  It integrates with PAM to know the set
of users that are logged in to a system and whether they are
logged in graphically, on the console, or remotely.

This reverts commit 408cc174.

See-also: https://bugzilla.altlinux.org/show_bug.cgi?id=28805#c45

A separate ConsoleKit2-service package should help here...

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

https://bugzilla.altlinux.org/28805 was fixed long ago.

ldv@ has dropped sysklogd from sisyphus due to
its long-standing FTBFS and "other problems":
http://git.altlinux.org/tasks/archive/done/_207/211999/logs/events.6.1.log

The current recommended replacement is rsyslog
which is fine by itself but really overcomplicated
for the barebones logging system we usually need...

Added chkconfig (spotted in alt-server's m-p-d)
and vconsole-setup-kludge@X86 (common problem
stop-gap item, unfortunately).

The infamous systemd infiltration through secondary
"targets" using virtual dependencies started with
syslogd-daemon, continued with network-config-subsystem
and later with ntp-server; all of its implementations
pulling in the main package which is explicitly unwanted
in sysv-based images.

Let's try employing pkgpriorities.

This target is only needed for systems based on sysV init
to replace logind; it conflicts with systemd-logind.

...for a "full" systemd target that's been re-aliased
as "+systemd"; please adjust any minimalistic images
to use/init/systemd instead of +systemd.

This partially reverts commit 30d38381: trying to use/rescue
with e.g. distro/simply results in conflict between SysVinit
and systemd-sysvinit; INIT_TYPE had to relation to RESCUE_LISTS
in the first place.  Ugh.

These lines don't effect anything currently due to #30806.

The "best" "feature" of systemd "init system" has just
emerged once again: it will happily sit there idling
given startup or shutdown loops resulting in what looks
like a hang to an unsuspecting user; let's provide the
suspecting one with at least some tools described at
http://www.freedesktop.org/wiki/Software/systemd/Debugging

It's the very same problem that must be solved within mkimage:
some package lists get expanded early and some late thus having
no chance to influence apt's choices of alternatives made early
(in fact, too early).

Until that, here's another kludge...

PS: turns out that ^systemd- is not "drop ^systemd" but rather:
    systemd-analyze
    systemd-coredump
    systemd-journal-gateway
    systemd-networkd
    systemd-sysvinit
    -- thus one /really/ wants something else.

This one relies on the controversial polkit-sysvinit package
that subverts policykit using well known groups to make it
"work" for things like NM and shutdown helpers.

See also http://altlinux.org/sysvinit and feel free to improve.

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 enables a spare shell on tty9 just in case.

The problem with initial implementation (commit 62e7e9c1)
is that there's no systemd-services package in p7/branch
thus apt complains about an attempt to remove something
that doesn't even exist in the first place.

That's a part of ALT Linux conveniences: system log
messages at tty12 (helps immensely in case of disk crash
or cable problems as running anything, including utilities
to view logs, becomes painful to impossible in such cases).

systemd lacks this kind of setup out-of-box for sure
so zerg@ hacked a substitute together; just pull that in.

That is, no need to pull in systemd as syslogd-daemon provider
when an unspecified one has been requested by interactivesystem
or anything else.

The tricky issue is that THE_LISTS will get expanded separately
and too late to specify a particular provider which will have been
auto-chosen while expanding e.g. BASE_PACKAGES.

This one is finally there and should help reduce the
systemd-induced mess in package lists and specifications.