Re: awscli v2 dependencies (was Re: Next team meeting: 2022-11-09 20:00 UTC)
- To: Ross Vandegrift <rvandegrift@debian.org>
- Cc: debian-cloud@lists.debian.org
- Subject: Re: awscli v2 dependencies (was Re: Next team meeting: 2022-11-09 20:00 UTC)
- From: Noah Meyerhans <noahm@debian.org>
- Date: Thu, 8 Dec 2022 14:12:06 -0800
- Message-id: <[🔎] Y5JhNjaolP+Byf8H@doom.morgul.net>
- In-reply-to: <20221128182442.g64toaidouddjbss@vanvanmojo.kallisti.us>
- References: <20221107060730.q3rqbxxqft7lziiv@stgulik.kallisti.us> <20221114055152.tjnp3ygu5qisj66m@stgulik.kallisti.us> <Y4TpibJ1L/LZOdCT@doom.morgul.net> <20221128182442.g64toaidouddjbss@vanvanmojo.kallisti.us>
On Mon, Nov 28, 2022 at 10:24:42AM -0800, Ross Vandegrift wrote:
> > So, some time has passed and I haven't managed to work on this at all.
> > Given the number of packages involved and the dependencies between them,
> > I'm not optimistic that we'll be able to package them all individually
> > as we discussed at the meeting. In order to facilitate the packaging of
> > awscli v2, I'm inclined to fall back to my proposal from #966573 [1].
> > Essentially this would package aws-crt-python as a single package with
> > the C code as a private component, rather than broken out into
> > standalone packages.
>
> Sounds good to me. As we discussed, this will be fairly easy to unwind
> when time permits individually packaging source pieces.
I just uploaded aws-crt-python targeting unstable. It'll need to make
it through the NEW queue, but that's the only remaining blocker for
awscli v2 work. I have a v2 branch mostly finished and will be able to
upload it as soon as aws-crt-python is accepted.
noah
Reply to: