5973ea42d7
Letting GErrors pile up is wrong; either exit the function or clear the GError (perhaps with a console warning). In this case we tolerate missing database files (because users are free to delete them), and build the checksum from whatever data is available. Seems weird, but that's how I'm told it's meant to work. Bail out on any other type of error. |
||
---|---|---|
design | ||
doc | ||
man | ||
packaging | ||
scripts | ||
src | ||
tests | ||
.gitignore | ||
autogen.sh | ||
configure.ac | ||
COPYING | ||
Makefile-decls.am | ||
Makefile-man.am | ||
Makefile-rpm-ostree.am | ||
Makefile-tests.am | ||
Makefile.am | ||
README.md | ||
TODO |
rpm-ostree, aka /usr/bin/atomic
An system to compose RPMs on a server side into an OSTree repository, and a client side tool to perform updates.
The project aims to bring together a hybrid of image-like upgrade features (reliable replication, atomicity), with package-like flexibility (seeing package sets inside trees, layering, partial live updates).
rpm-ostree is in beta!
While many of the underlying technologies here are stable, if you are considering using this in your organization, you should perform a careful evaluation of the whole stack. Software updates are obviously critical, and touch on many areas of concern.