hi robert,
On Fri, 17 Jun 2005 15:08:55 -0700 OpenMacNews wrote:
O> fyi: one more thing from Jordan ...
O> We generally don't go out of our way to report it when we fix
O> self-inflicted
O> build problems (since it's not a bug in anyone else's code), but they'll
O> certainly find out when the update is released.
O>
O> so it looks like 'keep a watchful eye out' is the advie of the day ...
Hmm... I'd ask them if the fix is in any net-snmp code, or the Mac OS build
environment... if the latter, then we need to incorporate the fix into cvs...
If the latter, then let us know what is needed for the fix, so we can add it
to the OS X README.
given the
"self-inflicted build problems (since it's not a bug in anyone else's code)"
i'd venture 'the latter' ... but i'm guessing.
as for 'asking them' ... i think *i* may have gotten as far as i can. but i
*will* keep 'poking' ..
Apple's notoriously close-mouthed when it comes to fixes in 'their code'.
personally, i'd suggest an offline email to Jordan Hubbard from a net-snmp
project 'offical' (e.g., you), as he _is_ their 'Director, UNIX Technology',
and see if some better 'collabrative communication' might be established
directly ...
Thanks for keeping on this...
de nada ...
richard
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
