b456badba3
I'd like to experiment with different things that end up reusing chunks of the rpm-ostree internals, such as libhif, the helpers we already have around RPM, etc. In this particular case I'm experimenting with unpacking/committing RPM packages as non-root. Eventually most of this should end up as internal private shared library, but it's convenient to have an ABI-unstable and hidden "internals" command to run things directly. This commit though just adds the scaffolding for "internals". |
||
---|---|---|
buildutil | ||
design | ||
doc | ||
libglnx@91e060699f | ||
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.