3e289ffab0
Now that the internal reading methods operate on the mainloop, and we know there can only be one write transaction at a time, it should be safe to drop the internal mutexes (and multithreading). Updates to the `OstreeSysroot` instance and DBus API all happen off the mainloop now. The write transactions now use a separate `OstreeSysroot` instance, and do not perform any changes to process state on their own. We always reload state from disk. I think this is a lot simpler to reason about from a correctness point of view, at a likely negligble loss in performance for read transactions. |
||
---|---|---|
.. | ||
main.c | ||
org.projectatomic.rpmostree1.conf | ||
org.projectatomic.rpmostree1.service.in | ||
org.projectatomic.rpmostree1.xml | ||
rpm-ostreed.service.in | ||
rpmostree-package-variants.c | ||
rpmostree-package-variants.h | ||
rpmostreed-daemon.c | ||
rpmostreed-daemon.h | ||
rpmostreed-deployment-utils.c | ||
rpmostreed-deployment-utils.h | ||
rpmostreed-errors.c | ||
rpmostreed-errors.h | ||
rpmostreed-os.c | ||
rpmostreed-os.h | ||
rpmostreed-sysroot.c | ||
rpmostreed-sysroot.h | ||
rpmostreed-transaction-monitor.c | ||
rpmostreed-transaction-monitor.h | ||
rpmostreed-transaction-types.c | ||
rpmostreed-transaction-types.h | ||
rpmostreed-transaction.c | ||
rpmostreed-transaction.h | ||
rpmostreed-types.h | ||
rpmostreed-utils.c | ||
rpmostreed-utils.h |