There are almost no interesting usage cases for multiple transactions (at least
until one attempts threaded installs, which are currently prevented by an
exclusive fcntl lock in RPM4 anyways).
What that means for bindings is that you can take out a static global
transaction which can be used where needed w/o a need to pass an rpmts through
all the methods.
That's basically what yum through rpm-Python bindings, once you dig through all
3 layers of sub classing that yum developers deem to be necessary.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Rpm-maint mailing list