On Fri, Dec 30, 2016 at 10:48:39AM -0500, Aaron Conole wrote: > Ben Pfaff <[email protected]> writes: > > > On Tue, Dec 13, 2016 at 01:45:05PM -0500, Aaron Conole wrote: > >> Also, FYI (and this is sortof a side-note) the libtool ABI versioning > >> information hasn't changed since 2014; bumping / managing that may > >> become an additional release burden if we start building on top of it, > >> and expect to ship it around. Imagine an install of this python package > >> from ovs 2.7.0 and a future openvswitch package 3.0.0; they currently > >> both see libtool version tag of 1:0:0 > > > > Should we bump the libtool version now? We're nearing a release, so > > it's about the right time. > > Sorry for the late response. I think it's probably appropriate to bump > at least the libtool 'age'. I'm not sure what kinds of ABI changes have > happened since introduction though - the interface 'major' version may > need to change.
I'm pretty sure we've busted ABIs left and right since 2014, so a major version update should be appropriate. > > libtool version numbering rules: > > https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html > > Thanks for the refresher. It's always a pain to remember which field > means what in the libtool parlance. Yes. I can remember the Unix rules, but not the libtool ones. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
