fee9f48409
These files were taken from json-glib, around the era of this commit: https://git.gnome.org/browse/json-glib/tree/build/autotools?id=2779d537492f1902d71cf648631238110b62b311 Unfortunately, this involved hacking it up a bit: - I couldn't easily use `nobase` for the data, so I deleted that. Test data goes in the installed-tests dir. - Delete duplicated predeclared variables; we're using nonrecursive make. - Ensure we run each test in its own tmpdir |
||
---|---|---|
buildutil | ||
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.