These have been purged from sisyphus:
http://git.altlinux.org/tasks/archive/done/_203/207990/

This is alike to the previous commit by antohami@
but affecting the intermediate server target:
no systemd-timesyncd when it's not asked for.

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>

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.

Fix stage2 meta-subprofile support while at that:
it was a questionable idea to use "/" as a delimiter
when part of the substitution is a pathname.

alterator-datetime pulls in ntp-server which is a virtual
dependency provided by both openntpd (which was assumed)
ntpd and systemd-timesyncd (which is undesired in those
images and pulls systemd either).

Be explicit.

...and clarification (had to look up the prio list in apt sources).

...and not any stray ntp-server
(which tends to end up with systemd-timesyncd).

"Provide iso contents file" has been a long-standing
feature request regarding both starterkits and distros
proper; release managers used to compensate this with
their own scripts.

Suggested-by: sem@, legion@ and someone else too

It's no more in sisyphus as of 5.8.0:
https://lists.altlinux.org/pipermail/devel/2018-June/204500.html

...as it is done for spt in m-p-d.

This metapackage depends on librtpkcs11ecp which is
proprietary x86-only blob as of today's sisyphus.

find's argument order is a bit different indeed.

Not that it was critical here but rather to reduce bit rot.

See-also: https://lists.altlinux.org/pipermail/devel/2018-June/204486.html

Added on Speccyfighter's request:
https://forum.altlinux.org/index.php?topic=41577

It was only found in regular+tde, let's generalize a bit.

Suggested-by: Speccyfighter, antohami@
See-also: https://forum.altlinux.org/index.php?topic=41577.0

Thanks squire for having mentioned this omission
and antohami@ for bringing attention to the report:
https://forum.altlinux.org/index.php?topic=41577.0

It (mis)stated that this feature does *not* influence install2
when it *does* since f5fd7764.

It's no more in sisyphus (and generally obsolete):
http://git.altlinux.org/tasks/archive/done/_202/207378/

- fixup release

...there's now proper DE maintainer out there ;-) // mike@

The common problem was network-config-subsystem getting
resolved into something completely wrong (like net-scripts
or systemd-networkd) *before* it got specified precisely;
let's just avoid the common cause, that is, a metapackage.

See-also: https://bugzilla.altlinux.org/show_bug.cgi?id=30806

install2 and live are both stage2 flavours, and I see no reason
rescue (the last one) should be any different here.

It's not much use for it to stay without the actual
pointer to the place where NM GUIs are referenced,
I've almost started out implementing the "missing"
bit myself right now :-/

Don't go crazy if Dir::Etc::sourceparts/d
gives something strange (e.g., /).

af_packet rather belongs to networking stack
than to common module library indeed.
Suggested-by: Alexey Gladkov <legion@altlinux.org>

services feature works like this:

  1. enable whatever services are in DEFAULT_SERVICES_ENABLE
  2. disable whatever is in DEFAULT_SERVICES_DISABLE
  3. enable services in SERVICES_ENABLE
  4. finally, disable those in SERVICES_DISABLE

So one should not disable display-manager service!

Disabling prefdm is not needed as it doesn't start
when display-manager.service symlink exists.

- pkgpriorities feature (manowar@)
- extended e2k support

Yes we've got e2k-*.iso images by now!
Should see quite some deduplication though.

Elbrus-801 and -101 are now added; 401's support refactored
and modified to cover 4.4 server system as well.

These clearly aren't final but have been stabilizing
for quite some time already, let's just merge.

There's no qemu there so far, and there's no need
to fiddle with setarch either.

NB: part of this commit erroneously went into
    1c777c8a
    quite some time ago, sorry about the mess.

It's legit here as I know no Elbrus users among
non-Russian-speakers, at least so far; should move
to generic l10n feature (which will definitely see
its glory by then).

This is to avoid extra actions when one actually needs
KOI8-R (which is still hardwired in some lcc messages).
Should all be rolled into l10n feature some day...

The early scheme consisted of boot.conf template
with a separate hook filling it in; this was nice
for serial console setup script which could just
amend the kernel command line as needed _but_
this got changed towards the more generic scheme
(breaking the hook in question, unfortunately).

manowar@ had some experiments with usbflash-based installer,
and we needed a git-server chroot as well.

Let's provide a more competent multi-system rescue image
while keeping some rescue bits common to all of the others.