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 good form to override this in the Debian package or should I conform to what upstream is doing and deal with the fallout once a reverse dependency is actually introduced and a new release comes out?

I've read the shared library policy section but since this is my first
library package I'm not sure I fully get all the implications of these
choices.

Thanks,
--Daniel

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEV6G/FbT2+ZuJ7bKf05SBrh55rPcFAmJHBBQACgkQ05SBrh55 rPdQZA/+I94Aflqh+FoXdT/abFU/9x5wKCd9fwtm1q8iMZmKkUAceGoHGB713ZDH kGDdO/9v5j4LMoISx21bF10zLBMFpRAfkxQ2Z0reSR7vosQ175gmA4Un4qCWLjLP 2izUS6ChactI4iclWyr2w6qtQqE4giTqRVNl9s7JCLHJU8ILun3rem4o5C2MB85h 8L0LkvRDT2kOuVNBhuDeBcGLToe0xIkvicsycWjl+uhK0mdpKEgnKyReyY65Xh62 OLL0zH7JdZ83ne0t5Ss0q0+fw3rn2NU4NKf36OY2WvDgj5x/ANQmyQA3j1uC+XLw tmC7OVwZWJ/w4KTBjn+jbmhU6POmk6+7DXYJ+A0dJbCUEShZ0muwkGTFKkC9zqUz gKMtQOQmYgHFc8GK6dtVjYmWyGHhsuVvXXCd/KaMsxN1XGRkSaMbEKe1HXDl6IY9 W4ffatkrUf6nCVL1+VITAnN1GqCFaqzzTDw4buekIFGyEXkhERY5/pXByEDH/aZT a2PvneUz/Fd62P0gkmIiR3upp5s495B8kEkQNJkKb/PPD/aIRn1LAxtqaA38imAS Q9hboGGkO+irf+OeRTShvHF214zTvYzdIT4tXIvzc32wqvbhfh5X94XBb61AbdPD hNSyKBbYRmtga24Gg68eOSk8MpXK9ySk0VASeJOmjndAQQv3b0U=
=T6ca
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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 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.

Is it good form to override this in the Debian package

No, both because Debian-specific sonames are often a bad idea and because
to do this correctly you need to track the ABI yourself.

or should I conform to what upstream is doing and deal with the fallout
once a reverse dependency is actually introduced and a new release comes
out?

Ideally this should be fixed at the upstream side, unless they explicitly declare that they don't keep the ABI stable.

--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmJHCy4tFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh KYoP/0qPhrsNaDV4hvUXvfP3BMhnlNgYkE5o5NtXNx2FLPDYyNvSJH8n4NfCcdOG CgnNTLakh5+NTQMfsTjFa+bDmeI77mk06TLne8S7F8SSblHq35QswWlnuDnrMraB IDnrArftNZWFxpAJzNMhfd90MzZjOf8CK+78NYwlC2Fc62DzV8b73605ecIkLD8l h2PTfxcKl3PrD2tAVOY9f1GdW4sOfARjgseQuVKPlzG+QeC9/LXW6Q8leBfOmFBk PPl9QRx/XwLpFpwGMeiJgFL016kcjbiVPH61UteZEhf8c6I4pgk5EzwqhBl+Islk FlBfa8gI5dcvg63ZC2Tx0piUa9bK9/tk7mllNBag91nOF5kz0kXHK5mFeIFx3Mu/ DrR4uyMMYmuIymTsNBB952ryP4jr/CY7MxQPsiMVDSWCGUkblZnDd2fP7nol5jAY efrdulTywVUiWciDjFBAtt8npm+45bzG/E32eG24p65Ezam8IdPSfqHVyichPpPd 9WBwTeSDFHKPTylZGz7G6TKiYNJHXPGGpFYVlAGwIV6Lmv4ck0uC1y5Its1OPbIl XJKNaD1WPksLL3TZkNtyAZLXYD5Rprqzgpte/M7iKuxtvPoxpIkVMe7G/pWX/GYN 0Tk8yPDWvDTW0dZoxzpUVx4S2ayq1F1Ll1UoDJIHdH8yTw9Q
=GzGr
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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 package updates I need:

https://github.com/savoirfairelinux/opendht/issues/600

I'll keep you posted Daniel as I've not a lib package either?

--
Kind Regards,

Gavin Henry.
https://sentrypeer.org

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

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 behaviour
changes. This thing is supposed to allow other projects to build plugins against their API after all so they'd kind of have to.

Is it good form to override this in the Debian package

No, both because Debian-specific sonames are often a bad idea and because
to do this correctly you need to track the ABI yourself.

Yeah I think I'm just not going to bother for now we'll see if anything
does end up using these libs in the future.

On Fri, Apr 01, 2022 at 03:35:41PM +0100, Gavin Henry wrote:

I was just chatting with Andrey and colleagues in #debian-mentors about something similar

Let me know if you find any other good options in this space :)

Thanks,
--Daniel

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEV6G/FbT2+ZuJ7bKf05SBrh55rPcFAmJIp2YACgkQ05SBrh55 rPfEXw//RXHkvlq5h9YU1RWjEyFVVOjaBYoTjfQ8yZF1vde1IFx5aAEmx1FM8dL+ 3cKiumQGv4xtd1+orsOn43APi+onNGcDt1H1Zg+0eFpHsRDITE4oUQWiCYYD6AWm uK6ecqFnASwqlus3gGK432Sqlf25F+uxPshRQWs415RQ38EQohaNoJVdCGu7IyW4 pgWbPxwCJTs5bQuyoONVYsO3+7lMnx+gds+oOxEPsLJRhc5uycLxhjvMh9ZjB5bw 13+VXcyFDop6/zX0qjdDL1p/XhNvQoK6HFKYmVM1IA86TSxvL0+3vT42zxPUGA6S gYFM7J2UErf3Y/GP0bLcZODTSMB+bOzWSJgCM9G6L79nOmW1+A6ZdTMD19+/sqJD 9k3ZkrZJtP3mR/K+a3EC5UzfW70SAQb/YE2u1eIVbsUHx082QBIP9fc2rWeVrP4A 8g+dyZcytdwo0Jgl1Frj2itNhHDR/0WbaVHllZ6AezlPOh+mtA3oaQl9jMvpFsKs iJZdbzh5kHvGRppuNT2zbWnwUMJ91dgduM6nl+4UPcI4ZlxuMNW4AKpBRYFKhOCz f9cT5E+XxDCTQc+3bL8TE2IbNgFayUyfdMfwbjjFYobiFiBbv352HZINqKiqcwRX DayexfYU209xWid5PyccGT1llaEpLJ5pfOvUVyin/JGXguH+1KM=
=soGj
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)