Dave Shield wrote:
If we're going to ship the new code with 5.2.2, then it *MUST* be hacked to use the original command options, IMO.
I agree in principle, but instead of "hacking" the new code for the old options we may also ship a *wrapper* program (in C/sh/whatever) that translates old to new options and calls the new code with this. This'd have the advantage that users could *choose* whether to use the old or new options, especially in mixed 5.2.x/5.3.x environments or when migrating existing scripts. snmpnetstat in 5.2.x and earlier would default to old options and 5.3+ to the new ones. What do people think?
+Thomas -- Thomas Anders (thomas.anders at blue-cable.de) ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
