On 16/09/10 09:31, Denis Arnaud wrote: > [...] > Hence, since last year, the soversion now matches the Boost version. For > instance, the soversion of Boost 1.44.0 is xxx.so.1.44.0 > But I'd be perfectly happy with the soname being just xxx.so.major.minor
AFAIK, Boost does not issue bug fix releases. As a collection of libraries, every release introduces variety of changes, also those touching API/ABI. I like the idea to use version number as soversion. However, SOCI is a single library and we should expect we will issue patch releases that do not touch ABI. Thus, it would make little sense to bump soversion if we release form 3.1.0 to 3.1.1. As we've already discussed and more or less agreed, we can make soversion in SOCI similar, bumped on every MAJOR.MINOR only. Moreover, not a separate number would be kicked up but we can do what Boost does...use release version: release version 3.1.0 gives soversion libsoci_core.so.3.1.0 release version 3.1.1 gives soversion libsoci_core.so.3.1.0 release version 3.1.2 gives soversion libsoci_core.so.3.1 (Zero can go) release version 3.2.0 gives soversion libsoci_core.so.3.2 release version 3.2.1 gives soversion libsoci_core.so.3.2 release version 4.0.0 gives soversion libsoci_core.so.4.0 release version 4.0.1 gives soversion libsoci_core.so.4.0 Folks, does it sound for you? 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
