@justsoup lix is promising too iirc. I'm just using mainline nix for now, since I'm developing #QuadOS anyways.
#QuadOS is coming along nicely, I've decided how it'll work, and live iso is booting. Working on installer now, and then I'll start on functionality. Thanks to @Heliguy and @winsdominoes for helping and testing as always!!
Hello fedi! I'm making my own immutable distro, and I've got some questions:
other than that, assuming I use bluebuild for now, would a structure like this work?
core - has core system stuff, like kernel, bootloader, etc. Included in image, needs reboot to apply
other/system - has other stuff like system flatpaks, config files, anything that doesn't need a reboot to change
Each would be cached so only core or other would be rebuilt depending on the last value.
other would use an overlay inside a btrfs sub volume. I was thinking I apply changes directly to the subvolume and rollback if they interrupt or an error occurs, but now I'm thinking a power cut or other force shutdown might mess that up.
Any thoughts would be appreciated, thanks! You're helping to shape QuadOS! QuadOS currently has the following devs: Me, @Heliguy, and @winsdominoes. It aims to be like NixOS, but using flatpaks, and hopefully less janky.