On 17/09/10 01:20, Mateusz Loskot wrote: > On 16/09/10 17:11, Denis Arnaud wrote: >>> As we've already discussed and more or less agreed, we can make >>> soversion in SOCI similar, bumped on every MAJOR.MINOR only. >> >> We are 100% in line. > > Good. > >>> 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 >>> release version 3.1.1 gives soversion libsoci_core.so.3.1 >>> 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 >> >> That sounds perfect to me. > > Great, then if no sudden proposal of better approach happens. > I will implement this idea.
Folks, Done. I have updated soci_version() macro and now it sets MAJOR.MINOR as SOVERSION. Later, I will make use of SOVERSION for libraries naming on Windows. ATM, SOVERSION is used on Linux (Unix) only. 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
