6a4df91cc4
There are many reasons why the daemon may not be able to start up. An initialization error doesn't/shouldn't reflect a programming mistake, but instead a runtime issue in the environment. Thus, if we fail to start the daemon, we shouldn't use g_error(), which dumps core. We should instead print the GError and clean up as nicely as we can. Resolves https://github.com/projectatomic/rpm-ostree/issues/194. |
||
---|---|---|
buildutil | ||
design | ||
doc | ||
libglnx@3c470803d0 | ||
man | ||
packaging | ||
scripts | ||
src | ||
tests | ||
.gitignore | ||
.gitmodules | ||
autogen.sh | ||
configure.ac | ||
COPYING | ||
Makefile-daemon.am | ||
Makefile-decls.am | ||
Makefile-lib-defines.am | ||
Makefile-lib.am | ||
Makefile-libpriv.am | ||
Makefile-man.am | ||
Makefile-rpm-ostree.am | ||
Makefile-tests.am | ||
Makefile.am | ||
README.md | ||
TODO |
rpm-ostree
A 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.