https://bugzilla.redhat.com/show_bug.cgi?id=2049400
--- Comment #14 from Dominik Wombacher <dominik(a)wombacher.cc> ---
(In reply to Nikola Forró from comment #13)
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.
You are right, for aws-crt-python it looks like that all aws lib dependencies
come from git-submodules.
Technically it doesn't ship the libraries, it ships
_awscrt.abiN.so the
libraries are statically linked into.
True, so from a packaging Guideline perspective this falls then somehow under
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_packaging_sta...
?
Or is it bundled when it's linked against fedora external packages/sources and
static libraries if they exist as package in fedora?
I think it is possible for python-awscrt to bundle the libraries and
at the
same time have them packaged separately, is it not?
Yes it is, I guess that's why I was a bit confused about your comment that
packaging of aws-c-cal shouldn't proceed.
So that means, there is no reason not to finalize the process and add aws-c-cal
to the already created repo?
And we should actually do the same with the rest of the libraries and if
possible use them during package building?
--
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...