On Fri, 04 Nov 2005 14:19:30 +0100 Thomas wrote:
TA> I agree in principle, but instead of "hacking" the new code for the old
TA> options we may also ship a *wrapper* program (in C/sh/whatever) that
TA> translates old to new options and calls the new code with this. This'd
TA> have the advantage that users could *choose* whether to use the old or
TA> new options, especially in mixed 5.2.x/5.3.x environments or when
TA> migrating existing scripts. snmpnetstat in 5.2.x and earlier would
TA> default to old options and 5.3+ to the new ones. What do people think?
I think it's ugly, but probably better than the alternative of shipping w/out
snmpnetstat.
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
unless they are requests for paid consulting services.
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:
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
