>>>>> On Sat, 27 Aug 2005 00:20:30 +0200, Thomas Anders <[EMAIL PROTECTED]> >>>>> said:
Thomas> 1) leave things as-is (everyone seems to have voted against Thomas> this) Agreed. Thomas> 2) drop libtool and set SONAME by other means (likely yielding to Thomas> portability problems) bzzz Thomas> 3) hack our local libtool copy do produce SONAME libsnmp.so.5.x Thomas> (would probably make libtool updates a nightmare in the Thomas> future) bzzz (FYI, I started to hack libtool a long time ago to add the extra suffixes that no one has been able to figure out how to get it to do. I finally decided to give up on that path because of the huge number of architectures it handles and how each one is dealt with in funky ways. Though I was sure I could get it to work, I doubted getting it right on everything everywhere as well as worrying about upgrading to new libtool versions in the long run). Thomas> 4) follow libtool versioning recommendations Thomas> (http://www.gnu.org/software/libtool/manual.html#Versioning) sigh. but I don't see a better choice either. The problem is that I actually expect we break things a lot and that even following their advice won't work well since we maintain so many trees. EG, consider the agent library and how often we add stuff to the structures and APIs there. It's not on sub-major releases only. So.... I think we need to probably do different things at this point. [I'm about to say a lot of stuff without testing it or reading the libtool documentation again. You've been warned] 1) Have *every* (maintained) branch start using a new libcurrent value. Thus we can assign current=8 to 5.1, current=9 to 5.2 and current=10 to what will be 5.3. Then update revision and age to 0 for all of them and then follow the instructions. um, ok, that was everything in 1) -- Wes Hardaker Sparta, Inc. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
