Re: Dealing with library using upstream version as SOVERSION

2022-04-02 Thread Daniel Gröber
Hi Gavin and Andrey, On Fri, Apr 01, 2022 at 07:24:55PM +0500, Andrey Rahmatullin wrote: > This suggests they don't know or don't care about ABI stability. Yeah, that's my guess too. On the other hand reading through their, pretty detailed, changelogs does seem to suggest they keep track of

Re: Dealing with library using upstream version as SOVERSION

2022-04-01 Thread Gavin Henry
> > However upstream just uses their release version in SONAME which doesn't > > seem very useful. > This suggests they don't know or don't care about ABI stability. I was just chatting with Andrey and colleagues in #debian-mentors about something similar and have raised this upstream for the

Re: Dealing with library using upstream version as SOVERSION

2022-04-01 Thread Andrey Rahmatullin
On Fri, Apr 01, 2022 at 03:54:35PM +0200, Daniel Gröber wrote: > Hi debian-mentors, > > I'm working on packaging [vpp] which installs a number of shared libraries > that may want to be used by other Debian packages in the future. > > [vpp]: https://github.com/fdio/vpp/ > > However upstream just

Dealing with library using upstream version as SOVERSION

2022-04-01 Thread Daniel Gröber
Hi debian-mentors, I'm working on packaging [vpp] which installs a number of shared libraries that may want to be used by other Debian packages in the future. [vpp]: https://github.com/fdio/vpp/ However upstream just uses their release version in SONAME which doesn't seem very useful. Is it