The main obstacle that I see right now is the lack of integration with GNOME Software and the rest o
The main obstacle that I see right now is the lack of integration with GNOME Software and the rest of the GUI package managers
KKK
III
AAAIAAII
FROM image
NINNNA
RAAAAI
NAIARANNIOverall, rpm-ostree is used in several important projects and will continue to be maintained for many years to come.
However, for use cases which want a "pure" image based model, using bootc will be more appealing. bootc also does not e.g. drag in dependencies on libdnf and the RPM stack.
bootc also has the benefit of starting as a pure Rust project; and while it doesn't have an IPC mechanism today, the surface of such an API will be significantly smaller.
Further, bootc does aim to include some of the functionality of zincati.
But all this said: It will be supported to use both bootc and rpm-ostree together; they are not exclusive. For example, bootc status at least will still function even if packages are layered.
NNIRAAIAANAR
S
