[Pkg-xmpp-devel] libsignal-protocol-c transition? (dino-im, profanity, psi-plus)
W. Martin Borgert
debacle at debian.org
Thu May 30 17:48:56 BST 2019
many thanks for your quick and elaborated answer!
On 2019-05-30 15:55, Boris Pek wrote:
> On 2019-05-30 01:42, W. Martin Borgert wrote:
> > A. We can just increase the major version number to 3 and ask
> > upstream to skip the 3 and jump directly to 4 with the next
> > release. (Not sure, whether they will do that.)
> I would be positively surprised if they will do this for us. =)
I only today asked for that, let's see.
> > B. We can add minor and micro number to the library symlink,
> > so that applications link against the exact version.
> Yes, this would be the most obvious choice for us. I was going to use full
> library version in its SONAME (libsignal-protocol-c.so.2.3.2).
> > (No idea how to do that exactly with cmake.)
> It is trivial:
Indeed, this seems to be the best solution. I'll name the binary
package according to the soname libsignal-protocol-c2.3.2 then.
Also, the symbol file does not make much sense then, right?
I'll probably just remove it.
> > C. We can version 2.3.2 let conflict with the current versions
> > of the three dependencies and let those depend on the newer
> > version. (No need to go through the new queue.)
> I would strongly suggest you do not do such things.
It's the least "clean" solution and it does not scale.
> I thought to update libsignal-protocol-c package in experimental myself few
> months ago, but still have not found time for this as you see. So please go
> ahead. =)
I'll try to! :-) Cheers
More information about the Pkg-xmpp-devel