Tooling for development and testing on immutable OSes
In order to shorten the development cycle, it would be nice to build new tooling (on top of builstream
, sysext
, and nspawn
) to allow developers to work on system components by building multiple projects, layering them atop their filesystem and restart the session into that temporary layered tree.
This is not only a better workflow and saves a lot of development time, but also allows low level component developers to easily do their work on image-based systems like GNOME OS.
It's good to start with reading the documents about systemd-sysext
- https://0pointer.net/blog/testing-my-system-code-in-usr-without-modifying-usr.html
- https://blogs.gnome.org/alatiera/2023/08/04/developing-gnome-os-systemd-sysext/
This task should include:
- discuss with target developers what is needed / they want
- decide in implementation, POC
- final implementation
- documentation and publicity
Edited by Jerry Wu