On Tue, May 28, 2024 at 05:48:10PM +0200, Julius Pfrommer wrote: > > > The intent was to do the SONAME patching entirely in the rules file. > > > Now we instead ship a small patch to the upstream CMakeLists.txt that > > > modifies the linker flags. > > This doesn't answer why are you changing the SONAME in a Debian-specific > > patch at all. > > The upstream currently produces libopen62541.so.1. > > In order to allow the parallel installation of multiple versions it is better > to have libopen62541.so.1.4. ABI compatibility should drive SONAME changes, not the desire to install multiple ABI-compatible libraries at the same time. And Debian shouldn't deviate from the upstream unless really necessary.
> So a future version v1.5 gets libopen62541.so.1.5.
>
> The installed shared objects (and symbolic links) are now as follows.
>
> libopen62541.so -> libopen62541.so.1.4
> libopen62541.so.1.4 -> libopen62541.so.1.4.1
> libopen62541.so.1.4.1
>
> If this is acceptable we will change the upstream to always produce
> libopen62541.so.{major}.{minor} as the SONAME.
SONAME doesn't need to match the software version and shouldn't be bumped
when it's not necessary.
> This will take a few weeks until the next upstream minor release. The
> Debian-specific patch can then be removed.
>
> If you prefer a different SONAME and filename convention, just let me know.
The upstream should track the ABI compatibility properly and adjust the
SONAMEs accordingly. This is not what Debian prefers but a generic
requirement for Linux shared library projects.
--
WBR, wRAR
signature.asc
Description: PGP signature
