Ok, I pushed the first and the last patch as a sign of good will.
The problem here is that librpm (which rpmstrPool is part of) but also
librpmbuild are libraries that might be used in applications running other
threading implementations.
Also rpm already uses pthread - although not very consistently. So yes,
rpmstrPool needs some thread proofing. Still I am for now not comfortable to
push these remaining patches without further looking into possible implications
- especially on the librpm side.
--
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/226#issuecomment-370439774
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
