f1973d7557
The ProgressEnd signal indicates to clients there will be no more DownloadProgress or SignatureProgress signals in the transaction, and any further Message signals should be output as separate lines instead of replacing the previous progress message. In other words, it's just a way of driving GSConsole remotely. |
||
---|---|---|
buildutil | ||
design | ||
doc | ||
libglnx@0cf50c6735 | ||
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.