On 15/09/10 14:03, Maciej Sobczak wrote:
> On 9/15/2010 1:31 PM, Mateusz Loskot wrote:
> 
>>> AFAIK soci does not put too much effort in keeping ABI stable (correct me 
>>> if I
>>> wrong) in such case you probably should update SOVERSION almost any release.
>>
>> Yes, you're right, as far as my own understanding goes.
>>
>> Maciej, any comments to that?
> 
> I tried to stay away from this subject as long as I could ;-), but once 
> you called me by name, here's my opinion: I think that the importance of 
> soname/soversion is overstated.
> This is probably because I prefer static linking over shared libraries 
> whenever possible. Frankly, I consider shared libraries to be a source 
> of problems, not a solution to any valid problem today, as they should be.
> 
> (now you know why I tried to stay away from the discussion ;-) )

Hehe, yes I do.

Let's not start arguing about usability, ... of static vs dynamic linking.

I personally don't care about SOVERSION too, but I have decided to
listen to users and package maintainers. If they asked about that,
then it means to me they need it, they make use of it.
So, it would no hurt SOCI to follow users needs here.

> Having said that, I recognize that there is a place for different 
> opinions on this subject.
> I also trust Mateusz as a package manager and I am sure that whatever 
> policy will be chosen for the project, it will be good.

Thanks. So, we will work out solution suitable for Julien, Denis, Artyom
and others who have submitted ideas.

Best regards,
-- 
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Soci-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/soci-users

Reply via email to