[Debian-med-packaging] planning (a) hsqldb transition(s)

[Laszlo Kajan]

Ah, yes, about shared libraries. librarynamesoversion (or libraryname-soversion).

* I think this should be applied to hmmer as well, hmmer (in testing) -> hmmer3, since that's not compatible with hmmer(<< 3).

I have stuff that depends on hmmer (<<3), so I would need both hmmer(<<3) and hmmer/hmmer3(>=3) to coexist in one installation. Could this be
resolved before the freeze?

Thanks for the info! Best,

Laszlo

On 02/05/12 10:36, olivier.sallou at codeless.fr wrote:
> Le 5/2/12 10:29 AM, Laszlo Kajan a écrit :
>> Hi Olivier!
>>
>>> In case of API incompatibility, according to Policy, package should be
>>> named hsqldb2-xxx in this case.
>> I don't remember this bit - but would like to refresh my memory - could you give me a link/section number where this is described?
> 
> It is linked to [0], 8.1Runtime shared libraries.
> Mose specially:
> " Every time the shared library ABI changes in a way that may break binaries linked against older versions of the shared library, the SONAME of
> the library and the corresponding name for the binary package containing the runtime shared library should change."
> 
> The name of the binary package must be changed to.
> 
> 
> [0] http://www.debian.org/doc/debian-policy/ch-sharedlibs.html
> 
> Olivier
>>
>> Thanks a lot!
>>
>> Best regards,
>>
>> Laszlo
> 
> 
> -- 
> gpg key id: 4096R/326D8438  (keyring.debian.org)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
>