> Using the RPM transaction APIs from such a process is currently Undefined
> Behavior.
All such environments you listed also provide a way to constrain threading
behavior when you need to, because it's unrealistic to actually _mandate_ that
at the layers below it. Even Python, Perl, and Ruby have this. I know Java
_definitely_ does.
The phrase "undefined behavior" (in title case or no) isn't enough in itself to
justify breaking the librpm architecture.
--
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/1526#issuecomment-773510992
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
