[Pkg-scicomp-devel] Library soversion numbers in SuiteSparse

Daniel Rus Morales danirus at tol-project.org
Mon Feb 11 08:44:53 UTC 2008


Rafael Laboissiere wrote:
> * Adam C Powell IV <hazelsct at debian.org> [2008-02-10 13:07]:
>
>   
>> Why not just use the whole library version in the soname and package
>> name?  For example, libsuitesparse has lib*.so.3.1.0 which is the
>> soname, and forget about .so.3 .  Then the soname and package name
>> match, so lintian is happy, and if upstream changes the interface
>> between 3.1.0 and 3.1.1 (let alone 3.2.0), the soname and package names
>> change, right?
>>
>> This is what I do with petsc, spooles, hypre, parmetis, my netgen shlib
>> patch, and will have to do for opencascade...  And it's lintian-clean.
>>     
>
> Yes, this is the right thing to do for now, I think.  Thanks for the
> suggestion, I will implement it in suitesparse.
>   

But that's what indeed you did, isn't?
I see that change in the 02-AMD_Lib_GNUmakefile.dpatch file.

I've just send an email to Tim Davis, the upstream author. While we wait 
for an answer I think that what you did is better than the prior 
solution. Ayway I hope Mr. Davis will give us the chance to go further 
this. Let's see.

Cheers,
Daniel




More information about the Pkg-scicomp-devel mailing list