On 18 May 2017 at 09:11, Aaron Conole <acon...@redhat.com> wrote: > Hi Joe, > > Joe Stringer <j...@ovn.org> writes: > >> The current intent for Open vSwitch is to maintain libopenvswitch ABI >> stability for minor versions, for example each release within the 2.7.z >> series. According to the following documentation, no changes to exported >> headers should be made. >> >> http://docs.openvswitch.org/en/latest/internals/contributing/libopenvswitch-abi/ >> >> However, it is occasionally necessary to make changes to >> {include/openvswitch,lib}/*.h headers to fix issues within a given >> release series. The current libtool tagging mechanism in the build >> system does not allow for this without creating a conflict between the >> libtool 'current' version and the next minor release of OVS. >> >> This patch modifies libopenvswitch build to include the MAJOR.MINOR >> release version in the libX name, and include the libtool CURRENT and >> OVS MICRO release in the libtool versioning tags to indicate library >> stability. The resulting format is "libfoo-X.Y.so.CURRENT.0.Z" for OVS >> release "X.Y.Z". >> >> Developers should still attempt to avoid introducing ABI-breaking changes >> within a particular OVS-X.Y release series, but if this is not possible >> this patch introduced a mechanism to allow an ABI-breaking fix to be >> introduced. In such a case, developers may update the libtool CURRENT >> version to indicate this breakage to library users. >> >> Signed-off-by: Joe Stringer <j...@ovn.org> >> Acked-by: Ben Pfaff <b...@ovn.org> >> --- > > Acked-by: Aaron Conole <acon...@redhat.com>
I appreciate the review on this work Aaron, thanks! Applied to branch-2.7. _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
