> TA> Otherwise, shall we rather use an SONAME like
"libnetsnmp.so.5.<minor>" 
> TA> (e.g. libnetsnmp.so.5.2) and thus require applications to relink when 
> TA> upgrading from 5.x to 5.y?
> 

RS>Makes us two. However, this'd be a quite significant decision, so more 
RS>feedback/votes are highly appreciated. 

I vote yes.

RS>Also, if we'd decide to do it, 
RS>shall we start it from 5.3 onwards? Or for all upcoming 5.[123] releases?

All releases.  We have had changes that apply to all releases.  We have had
problems in the past with people linking to old libraries when they have a
mixtures of installs, some not properly removed.


This communication is intended for the use of the recipient to which it is
addressed, and may contain confidential, personal and or privileged
information. Please contact us immediately if you are not the intended
recipient of this communication, and do not copy, distribute, or take action
relying on it. Any communication received in error, or subsequent reply,
should be deleted or destroyed.



-------------------------------------------------------
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

Reply via email to