On Sat, 27 Aug 2005 00:20:30 +0200 Thomas wrote: TA> It looks like we're left with the following options: TA> TA> 1) leave things as-is (everyone seems to have voted against this) TA> 2) drop libtool and set SONAME by other means (likely yielding to TA> portability problems) TA> 3) hack our local libtool copy do produce SONAME libsnmp.so.5.x TA> (would probably make libtool updates a nightmare in the future) TA> 4) follow libtool versioning recommendations TA> (http://www.gnu.org/software/libtool/manual.html#Versioning) TA> 5) something better
Unless someone comes up with 5, I'd say #4 (using -release). Though I still have not found out how to make this happen automatically... -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- 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 Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
