This is a discussion on Re: caught between a rock and a hard place: new libtool versioning within the SNMP Coders forums, part of the Networking and Network Related category; Dave Shield wrote: > I must admit that I'm drawn to Wes' original position - a patches > branch shouldn'...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Dave Shield wrote:
> I must admit that I'm drawn to Wes' original position - a patches > branch shouldn't include incompatible changes, so ought to continue > with the same library number throughout. > In which case I'd suggest using '54' for the 5.4.x branch. > (Still relatively large, but not ridiculously so - so that's a > semi-serious suggestion, as opposed to last night's offering). > > That's the purist position. Pragmatically, that might not be 100% > sustainable. But just allowing one single library change within a > given patches branch feels extremely shortsighted. How would we > decide when to allow that one change? And what we would do when we > wanted to make another (possibly more vital) change in the same line. > Reminds me of the "Rule of One" in Lloyd Biggle's "Still Small > Voice of Trumpets"! > > > Now I'm no expert on library version management, but is it true that > we're restricted to a single version number? I'm sure that I've seen > shared libraries named something like > > libwombat.so.1 > libwombat.so.1.3 > libwombat.so.1.3.6.1 > > Isn't that exactly the sort of approach needed for this situation - > later libraries on a given patch branch should be "mostly compatible" > with earlier ones? > > But I might well have completely misunderstood how all this works. We've had this discussion before when we've been moving *away* from this sort of versioning and decided to follow the libtool recommendations instead. In your example above, the suffixes just aren't too relevant. You'd rather run: objdump -x libwombat.so.1.3.6.1 | grep SONAME SONAME libwombat.so.1 in order to realize that this is still the same SONAME (which can only have a single number as the suffix which should increase on incompatible changes). And for the whole of net-snmp 5.x we've always had a SONAME of libnetsnmp*.so.5 (until the change) which just wasn't right. We're now doing better (increasing between branches), but should be careful to not overact, I think. +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=...057&dat=121642 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/...et-snmp-coders |
![]() |
| Thread Tools | |
| Display Modes | |
|
|