The yum developers I've talked to about parallel transactions do not
want to cater to this use-case. I'm not having the same argument I had
2 years ago, so I'll leave things at that.
Can't the lock be limited to actual operations (update, install, remove etc) and any searching etc be done on a parallel copy of the yum database, where only actual transactions that lead to a change are locked?