I'm actually curious as to what the use-case for this patch is, because at
least with the cli tools of rpm itself, queries and the like have "always"
stopped fast enough with the existing polling mechanism.
Now that transactions run with signals blocked, we could move the signal polls
into the various iter-next functions if that helps, but that wouldn't help
anything if it's some other software (depsolvers etc) that's not polling for
interrupts in their own busy-loops.
--
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/pull/251#issuecomment-339296375
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
