Changes in the container stack

[Shengjing Zhu]

On Wed, Aug 2, 2023 at 10:02 AM Seth Arnold <seth.arnold at canonical.com> wrote:
>
> On Tue, Aug 01, 2023 at 06:45:59PM -0300, Lucas Kanashiro wrote:
> > With that in mind, we, the Server team, identified the need to decouple the
> > application (what users really use) and the library (what is used by rdeps)
> > in a way that, on the one hand, we can keep following upstream projects
> > without worrying about breaking changes and on the other hand, we keep the
> > library (-dev package) stable to avoid breakages of packages sync'ed from
> > Debian or already in stable releases during SRUs.
>
> Hello Lucas, I'm very concerned about this plan, I hope you can assuage my
> fears.
>
> This sounds like we'll introduce a new problem, where third-party
> applications built against the libraries will become incompatible with
> the main application.
>
> If the ecosystems are changing external library ABIs too often, I can
> only shudder in fear at how quickly internal library ABIs are changing.
>
> What gives us the confidence that the internal ABIs are actually more
> stable and reliable than the external ABIs?
>

Do these Go packages have ABI anyway 👀 Other applications interact
with them with either cli or HTTP/GRPC API.
The libraries are often changed, but I remember the cli and HTTP/GRPC
API are stable and backward compatible.

-- 
Shengjing Zhu