Oh yep, they are declarative, and that’s what we’ve tried to implement with /system.yaml. pacman hooks and grub configs can be defined through /system.yaml (through a combination of the packages and commands arrays), but Plasma config is per-user and so wouldn’t be possible to declare unfortunately :( you can declare GNOME config though, fwiw
oh yep, should’ve clarified, /system.yaml’s, as the name might suggest (lol), for system-wide config only, and GNOME just so happens to support system-wide config (dconf and gsettings overrides); we used to have a utility for declaring config for individual users akin to home-manager in blendOS v3, but dropped it with v4 since that wasn’t used much; still might make a return though :)
Does anybody know if configurations are also declarative?
Basically I want some easy way to spin up something arch linux based with my KDE Plasma settings, pacman hooks, grub configurations etc.
Oh yep, they are declarative, and that’s what we’ve tried to implement with
/system.yaml. pacman hooks and grub configs can be defined through/system.yaml(through a combination of the packages and commands arrays), but Plasma config is per-user and so wouldn’t be possible to declare unfortunately :( you can declare GNOME config though, fwiw(disclaimer: blendOS dev here)
nix has home manager for that, but even then, plasma configs are a huge mess there.
thanks for the reply and your hard work :)
oh yep, should’ve clarified, /system.yaml’s, as the name might suggest (lol), for system-wide config only, and GNOME just so happens to support system-wide config (dconf and gsettings overrides); we used to have a utility for declaring config for individual users akin to home-manager in blendOS v3, but dropped it with v4 since that wasn’t used much; still might make a return though :)
thank you for your support! :)
Why not just use home-manager on arch?