why the FUCK did i think making an init selector was a good idea
artix themselves dont even ship services in their online installer
they just give you a bare system and say "figure it out" and
it WORKS because people can just install their init of choice
afterwards. but nooooo i had to be clever and build a whole
netinstall-add monstrosity with openrc/runit/s6 service groups
that broke constantly because basestrap --overwrite is a lie
and init packages conflict with each other and sddm-openrc +
lightdm-openrc both Provide: init-displaymanager and pacman
just goes 🖕 during install.
so anyway. dinit only now. you want something else? read
changing-init.md, i literally copied the artix wiki tutorial.
i am not maintaining four init service groups in netinstall.yaml
for the rest of my life. this is my villain origin story.
actual changes:
- ripped out offline calamares mode (was never truly offline)
- ripped out packagechooser.conf (good fucking riddance)
- added packagechooser_dm.conf so you can at least pick your DM
- added BYODE offline installer (bare system + btrfs + snapper,
no DE, you pacman -Sy plasma-meta yourself)
- added yay + snapper + btrfs-progs to rootfs
- shoved Init Services + DM groups into netinstall.yaml (dinit
only, obviously)
- updated every markdown file that mentioned another init like
they were cursed (they were)
- wrote changing-init.md so i can just paste the link next time
someone asks
- X-KDE-IsAdminApplication=true so KDE stops acting like
calamares is a virus (its not, its just desperate)
The packagechooser_dm.conf has greetd as a DM option with
method: netinstall-select, but no matching 'greetd' group existed
in /etc/calamares/modules/netinstall.yaml (which is what Calamares
loads in online mode via modules-search: [local] resolution).
Without the group, selecting greetd silently fails and the
displaymanager module falls back to SDDM instead.
Add greetd + greetd-dinit group alongside the existing SDDM,
LightDM, LXDM, LY groups.
basestrap module (from calamares-extensions) reads netinstallAdd only
for the init provider name (e.g. 'dinit') to add elogind-dinit. It
does NOT install the subgroup packages from the user's packagechooser
selection (networkmanager-dinit, pipewire-dinit, etc.). So these were
selected in the GUI but never present in the target system.
Since the netinstall view's packageOperations -> packages module flow
works correctly, move all required *-dinit service packages into the
netinstall.yaml Default group (online) and profile.yaml rootfs (offline).
Also revert settings.conf back to services-artix + postcfg — these
modules DO exist (from calamares-extensions) and work correctly when
the service packages are installed. Remove the unnecessary shellprocess
files that were added as a mistaken workaround.
- Plasma group in netinstall.yaml now includes antergos-plasma-theme,
antergos-next-desktop-settings, and full KDE app list from branding
- Default group adds networkmanager, pipewire, pipewire-pulse,
wireplumber, firefox, mesa for working network/audio out of the box
- Init chooser packagechooser.conf adds pipewire-dinit and
wireplumber-dinit services to all four init sections (dinit, openrc,
s6, runit) for audio service enablement
antergos-release was missing from packages.yaml so the CI never
built it, causing error code 1 when the packages module tried to
install it. Now re-added to both CI config and Default netinstall
group.
antergos-release PKGBUILD exists but the package was never built
and deployed to the GitHub Pages repo. The packages module tried to
install it and pacman returned error code 1 (package not found).
Remove it until the CI builds and deploys it.
Also remove try_remove: artix-release from basestrap since it's not
needed without antergos-release in the Default group.
- Add antergos-release, antergos-next-keyring, antergos-wallpapers to
Default netinstall group (both global and online) so installed system
keeps Antergos branding instead of appearing as plain Artix
- Populate services-artix.conf (both online + offline) with service names
so SDDM, NetworkManager, dbus, etc. are enabled after install (fixes
boot-to-TTY issue)
- Create grubcfg.conf for online mode with GRUB_THEME default so
antergos-grub-theme is actually applied by grub-mkconfig
- buildiso: copy Antergos GRUB theme to ISO boot directory
- profile.yaml: add antergos-grub-theme to rootfs packages
- netinstall: move antergos-grub-theme from optional Style to mandatory Default group
- main.xml: set Antergos wallpaper as KDE system default
- set-antergos-wallpaper.sh: add QDbus fallback, wait for plasmashell
- .gitignore: ignore linux-next/ and winver/
c-ludenberg