https://bugzilla.redhat.com/show_bug.cgi?id=2049400
--- Comment #13 from Nikola Forró nforro@redhat.com --- (In reply to Dominik Wombacher from comment #12)
Based on https://docs.fedoraproject.org/en-US/packaging-guidelines/#bundling I understand we CAN do it but it wouldn't be reasonable. Separate aws-c-* packages mean we can re-use them for python-awscrt and all others right? Sounds like a much better approach then.
As far as aws-crt-python is concerned, upstream doesn't want to depend on specific versions of dynamic libraries and rather pulls in specific revisions of the libraries and links them statically.
Now I'm not sure anymore, it looks like some of them have open review request but stuck because of python-awscrt already ships them?
Technically it doesn't ship the libraries, it ships _awscrt.abiN.so the libraries are statically linked into.
I think it is possible for python-awscrt to bundle the libraries and at the same time have them packaged separately, is it not?