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

2022-01-22 Thread Roland Knall
To be fair, there are two things to consider here. The status quo and the future direction. The second one should not be to develop those libraries independently. I totally agree with you that this should not be our scope. The status quo though is a different one. I do feel that we should bring

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

2022-01-22 Thread João Valverde
Regarding questions I would like to know if is Wireshark is developed, including each of the three existing libraries, for other projects to add as dependencies to their software stack. It is possible I need to adjust my understanding and expectations accordingly, and I will do so. External pl

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

2022-01-21 Thread João Valverde
On 21/01/22 09:44, Bálint Réczey wrote: João Valverde ezt írta (időpont: 2022. jan. 21., P, 1:29): On 20/01/22 21:24, Bálint Réczey wrote: Hi Guy, Guy Harris ezt írta (időpont: 2022. jan. 20., Cs, 21:52): On Jan 20, 2022, at 12:34 PM, Gerald Combs wrote: Q: Should *wsutil* be part of

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

2022-01-21 Thread João Valverde
On 21/01/22 11:14, Bálint Réczey wrote: João Valverde ezt írta (időpont: 2022. jan. 21., P, 11:17): On 21/01/22 09:44, Bálint Réczey wrote: Hi João, João Valverde ezt írta (időpont: 2022. jan. 21., P, 1:14): On 20/01/22 12:41, Bálint Réczey wrote: Hi All, João shared his opinion abou

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

2022-01-21 Thread João Valverde
On 21/01/22 10:46, Roland Knall wrote: May I suggest that we focus on the discussion at hand here. The discussion about the package itself seems to be better suited for the issue list specific for that package, as is the purpose for that list. This is about package code that lives in the Wir

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

2022-01-21 Thread Bálint Réczey
João Valverde ezt írta (időpont: 2022. jan. 21., P, 11:17): > > > > On 21/01/22 09:44, Bálint Réczey wrote: > > Hi João, > > > > João Valverde ezt írta (időpont: 2022. jan. 21., P, 1:14): > >> > >> > >> On 20/01/22 12:41, Bálint Réczey wrote: > >>> Hi All, > >>> > >>> João shared his opinion abou

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

2022-01-21 Thread Bálint Réczey
Hi Roland, Roland Knall ezt írta (időpont: 2022. jan. 21., P, 11:48): > > May I suggest that we focus on the discussion at hand here. The discussion > about the package itself seems to be better suited for the issue list > specific for that package, as is the purpose for that list. > > The issu

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

2022-01-21 Thread Roland Knall
May I suggest that we focus on the discussion at hand here. The discussion about the package itself seems to be better suited for the issue list specific for that package, as is the purpose for that list. The issue here is, that with change https://gitlab.com/wireshark/wireshark/-/merge_requests/5

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

2022-01-21 Thread João Valverde
On 21/01/22 09:44, Bálint Réczey wrote: Hi João, João Valverde ezt írta (időpont: 2022. jan. 21., P, 1:14): On 20/01/22 12:41, Bálint Réczey wrote: Hi All, João shared his opinion about the project's commitment to maintain stable shared library ABI within stable branches: https://gitlab.

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

2022-01-21 Thread Bálint Réczey
João Valverde ezt írta (időpont: 2022. jan. 21., P, 1:29): > > > > On 20/01/22 21:24, Bálint Réczey wrote: > > Hi Guy, > > > > Guy Harris ezt írta (időpont: 2022. jan. 20., Cs, > > 21:52): > >> On Jan 20, 2022, at 12:34 PM, Gerald Combs wrote: > >> > >>> Q: Should *wsutil* be part of that stabl

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

2022-01-21 Thread Bálint Réczey
Hi João, João Valverde ezt írta (időpont: 2022. jan. 21., P, 1:14): > > > > On 20/01/22 12:41, Bálint Réczey wrote: > > Hi All, > > > > João shared his opinion about the project's commitment to maintain > > stable shared library ABI within stable branches: > > https://gitlab.com/wireshark/wiresha

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

2022-01-20 Thread João Valverde
On 20/01/22 21:39, Roland Knall wrote: To be quite honest, I asked the developers myself. In this case they are a group of students who implemented that utility and did not know better. Personally I would much rather have new developments added to the main repository than be implemented as st

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

2022-01-20 Thread João Valverde
On 20/01/22 21:24, Bálint Réczey wrote: Hi Guy, Guy Harris ezt írta (időpont: 2022. jan. 20., Cs, 21:52): On Jan 20, 2022, at 12:34 PM, Gerald Combs wrote: Q: Should *wsutil* be part of that stable ABI? Debian, Ubuntu and (according to rpmfind.net) OpenSuSE and Mageia treat it as such.

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

2022-01-20 Thread João Valverde
On 20/01/22 12:41, Bálint Réczey wrote: Hi All, João shared his opinion about the project's commitment to maintain stable shared library ABI within stable branches: https://gitlab.com/wireshark/wireshark/-/issues/17822 I believe the current practice is reasonable and beneficial enough for man

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

2022-01-20 Thread Roland Knall
To be quite honest, I asked the developers myself. In this case they are a group of students who implemented that utility and did not know better. Personally I would much rather have new developments added to the main repository than be implemented as standalone. And as Guy rightfully guessed, the

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

2022-01-20 Thread Guy Harris
On Jan 20, 2022, at 1:12 PM, Roland Knall wrote: > But it was implemented by utilizing heavily a wireshark installation > including libwireshark and libwsutil So why, *other than "because it uses Wireshark libraries intended to provide directly useful services such as reading capture files or

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

2022-01-20 Thread Bálint Réczey
Hi Guy, Guy Harris ezt írta (időpont: 2022. jan. 20., Cs, 21:52): > > On Jan 20, 2022, at 12:34 PM, Gerald Combs 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 kno

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

2022-01-20 Thread Roland Knall
Just to add to utilities that utilize such a library is https://github.com/epl-viz/EPL-Viz I agree that such an utility could be added to Wireshark itself, and it is not actively developed anymore (at least to my knowledge). But it was implemented by utilizing heavily a wireshark installation inc

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

2022-01-20 Thread João Valverde
On 20/01/22 15:28, Roland Knall wrote: I think it is reasonable to assume that libraries provided with the project are being used by external programs. I know one utility which is being used in a rather closed-off community (but nonetheless widely adopted by around 200-300 people), which got

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

2022-01-20 Thread Guy Harris
On Jan 20, 2022, at 12:34 PM, Gerald Combs 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 els

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

2022-01-20 Thread Gerald Combs
If I understand the discussion in issue 17822 and here, we're looking at the following questions (feel free to correct me where needed): Q: Should we commit to a stable ABI between minor releases? I think everyone agrees that we should, or at least that it's a worthwhile goal. Q: Should *wsuti

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

2022-01-20 Thread Roland Knall
For clarification: " but the change should most certainly happen with a version beyond 3.6" means, that the break should be reverted for 3.6.x, but it should be put in place for -dev to be in the next major release cheers Am Do., 20. Jan. 2022 um 16:28 Uhr schrieb Roland Knall : > I think it is

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

2022-01-20 Thread Roland Knall
I think it is reasonable to assume that libraries provided with the project are being used by external programs. I know one utility which is being used in a rather closed-off community (but nonetheless widely adopted by around 200-300 people), which got broken by this. Their solution is to stay on

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

2022-01-20 Thread Bálint Réczey
Hi All, João shared his opinion about the project's commitment to maintain stable shared library ABI within stable branches: https://gitlab.com/wireshark/wireshark/-/issues/17822 I believe the current practice is reasonable and beneficial enough for many parties to warrant the work, but I could b