Dave Shield wrote:
> I haven't looked through the longest script (nsb-functions)
> in the same detail, but I wouldn't expect anything untoward
> there either.
Random sample from nsb-nightly:
EXE_PATH=${0%nsb-nightly}
EXE_PATH=${EXE_PATH%/}
won't work with generic Bourne shell, AFAIK.
> If there is anything that's broken under /bin/sh, I'd prefer
> to see that fixed, rather than backing out and postponing
> this task for another time.
If it doesn't add too many complexity, I'd be fine with it as long as it
will get fixed *ASAP* (anything else will break tonight's nightly
builds). But I have no objections against the former requirement for
bash for nsb* either.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
