Hide Forgot
Description of problem: I'm thinking about multi-transaction package manager. It would require rebuilding whole RPM to make another way to write the database, but it could make life better. It would be innovation in packaging. How reproducible: Install packages, when some other app is using RPMDB. Actual results: Database access is owned. Expected results: Multi-transaction.
This is a feature request? What do you mean by multi-transaction? It sounds like you want to be able to do "yum install foo" and "yum install bar" at the same time?
Yes, exactly.
Actually rpm used to permit multiple simultaneous installations, but these days there's a global transaction lock to prevent that. Things get *really* hairy wrt race conditions etc when you start thinking about all the interactions with triggers and such in a truly concurrent access scenarios. What's the problem you're trying to actually solve by permitting concurrent transactions?