community VS repo-main

The Kiss Linux repos are not outdated, just the "official" one, there is one that is actively maintained by the community. https://github.com/kiss-community/community.

Yes. The init scripts are written so as to be as init-agnostic as possible. See here to see what has specifically been tested. You'll need to either change what owns /sbin/init or, when configuring the kernel, change what executable it spawns as PID 1. Depending on what init you use, you may have to set up a service manager or gettys manually like this -- custom scripts are placed in /etc/rc.d with self-explanatory suffixes .boot, .pre.shutdown, or .post.shutdown.

back is packaged in the community repository: https://github.com/kiss-community/community

If you use the Official unofficial community repository, watch out for packages that might get dropped by maintainers.

Again, if you had bothered to read the sidebar you would have seen links to both the community site as well as the community github repo.

I am very exited for https://kisscommunity.org, the possibilities are endless!

Kiss linux is what you are searching for

This might not be exactly what you are looking for but KISS linux (https://k1sslinux.org) is a distribution that doesn't force ANY init on you, supports disk encryption ofc, it's probably the most light and minimal distribution out there (the core install has 7 packages), it's rolling release.

perl - no, it can be patched out ncurses - for make config libelf - yes bash - fixed in 6.2, see https://github.com/kiss-community/repo/issues/79

Kiss is not abandonned, https://github.com/kiss-community/repo https://github.com/kiss-community/community

wget https://github.com/kiss-community/repo/releases/download/2021.5-1/kiss-chroot-2021.5-1.tar.xztar xvf kiss-chroot* --directory /mnt # Echos .profile into chroot echo "export KISS_PATH='' KISS_PATH=\$KISS_PATH:/etc/repos/repo core KISS_PATH=\$KISS_PATH:/etc/repos/repo/extra KISS_PATH=\$KISS_PATH:/etc/repos/repo/xorg KISS_PATH=\$KISS_PATH:/etc/repos/community/community export CFLAGS=\"-O3 -pipe -march=native\" export CXXFLAGS=\"\$CFLAGS\" export MAKEFLAGS=\"-j\$(nproc)\"" >> /mnt/etc/profile

Have a look at the source. These directories are created intentional. https://github.com/kiss-community/repo/blob/master/core/baselayout/build#L43 IIRC these directories are created on the distributions discretion.

Have a look at the busybox package https://github.com/kiss-community/repo-main/tree/master/core/busybox . See how "custom" configs are added to the sources file of the package? These files are available when building the package, or would override if available in the tarball. You can do the same for software which is configured with config.h/config.def.h .