https://bugzilla.redhat.com/show_bug.cgi?id=2049400
--- Comment #12 from Dominik Wombacher <dominik(a)wombacher.cc> ---
I have to do some more research to understand the history of those decisions.
But I'm wondering about:
I don't think the process should continue, as aws-c-cal is now
packaged as part of python-awscrt (bug #2179888).
There are a lot more aws-crt libs out there (aws-crt-ruby, aws-crt-php,
aws-crt-nodejs, aws-crt-kotlin, aws-crt-java, aws-crt-dotnet and aws-crt-cpp).
This decision means we would have to bundle the libs with any of them if it
would be build for Fedora?
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.
I want to keep aws-php-sdk3 alive
(
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...)
and one dependency of the newest version is aws-crt-php
Which has dependencies to 9 aws* libraries (aws-crt-ffi, aws-c-auth,
aws-c-http, aws-c-io, aws-c-cal, aws-c-compression, aws-checksums,
aws-c-sdkutils, aws-c-common).
My plan to tackle this package was to create separate ones for each library
dependency.
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?
--
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2049400
Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=rep...