> I have no insight to the other database formats so can't comment on how that
> is handled. For setups that never modify the running system but rather either
> prepare images or modify snapshots the transactional capabilities of rpm do
> not matter anyways. If anything goes wrong, no new snapshot/image gets
> produced.
But that's not even close to the common case that RPM is used for. Any feature
added to RPM must be considered holistically useful and made relatively safe
(within the context of RPM packaging management). Virtually everything is safe
in the model of using installroots and snapshots, but most usage of RPM is on
live systems, so that makes it difficult to justify this feature.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1151#issuecomment-609734724
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
