Bug#966573: progress packaging awscli v2
- To: 966573@bugs.debian.org
- Cc: Ross Vandegrift <rvandegrift@debian.org>
- Subject: Bug#966573: progress packaging awscli v2
- From: Noah Meyerhans <noahm@debian.org>
- Date: Tue, 1 Nov 2022 10:45:00 -0700
- Message-id: <[🔎] Y2FbHLzmoNe+symj@doom.morgul.net>
- Reply-to: Noah Meyerhans <noahm@debian.org>, 966573@bugs.debian.org
- In-reply-to: <Y2Czm/Uf6jUXxMI/@doom.morgul.net>
- References: <159613997435.30364.10545201843971877554.reportbug@bigtour.home> <YMt+qrg8RG0PRkA7@doom.morgul.net> <159613997435.30364.10545201843971877554.reportbug@bigtour.home> <20211006051043.dlghirp77mxoptta@stgulik> <159613997435.30364.10545201843971877554.reportbug@bigtour.home> <Y2Czm/Uf6jUXxMI/@doom.morgul.net> <159613997435.30364.10545201843971877554.reportbug@bigtour.home>
On Mon, Oct 31, 2022 at 10:50:19PM -0700, Noah Meyerhans wrote:
> > aws-crt-python is the hard part. It depends on a bunch of C libraries which
> > follow a more modern development style. They:
> > - provide no abi/api stability guarantees.
> > - have versioned releases, but no one cares about the versions. The intention
> > is that everyone should be following the main branch.
> > - only nominally support dynamic linking (it can be enabled, but is not used or
> > tested by upstream).
Actually, taking a look at Amazon Linux 2022's packaging of these
libraries, I see that they're distributed as .so files, and the
aws-crt-python packagin declares runtime dependencies on these
dynamically loaded libraries. So I don't think we're in uncharted
waters if we decide to ship .so libraries.
noah
Reply to: