Wireshark-dev: Re: [Wireshark-dev] Future of Wireshark's shared library ABI stability

From: Bálint Réczey <balint@xxxxxxxxxxxxxxx>
Date: Thu, 20 Jan 2022 22:24:41 +0100
Hi Guy,

Guy Harris <gharris@xxxxxxxxx> ezt írta (időpont: 2022. jan. 20., Cs, 21:52):
>
> On Jan 20, 2022, at 12:34 PM, Gerald Combs <gerald@xxxxxxxxxxxxx> wrote:
>
> > Q: Should *wsutil* be part of that stable ABI?
> >
> > Debian, Ubuntu and (according to rpmfind.net) OpenSuSE and Mageia treat it as such. It would be helpful to know what non-Wireshark packages depend on wsutil in those distributions and elsewhere.
>
> ...and, if there are any, to know *why*.

It seems libvirt's plugin needs wmem_alloc(), for example:
https://gitlab.com/wireshark/wireshark/-/issues/17889

IMO it is easier mentally to have a single library ABI policy because
we ship only public libraries. Having a more relaxed private shared
library policy would make it easier to make mistakes.

Also if libwsutil (with wmem_alloc) became private in 3.6.x then
libvirt had a much harder time continuing the maintenance of their
plugin starting with 3.6.0.

Cheers,
Balint