3e6f877282
The `QueryResult` class ended up being too awkward; having NEVRA strings meant for example that clients would have to parse them. It would be harder to present something like the current `rpm-ostree upgrade` package diff output. Now...I debated quite a while before doing this patch. The thing that's really awful about creating this library is there are *SO MANY* layers. rpm-ostree → libhif → hawkey → libsolv → librpm. It's enough to make one question whether one is actually accomplishing anything or just contributing to a collective insanity... Let's pretend for now it's the former. Closes: https://github.com/projectatomic/rpm-ostree/pull/136
rpm-ostree, aka /usr/bin/atomic
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.