> ypical Go shit there. If the scripts are so complicated that it's a > pain in the ass to find a way to run them, fix the stupid scripts.
They did, by building the "go" command. Do you think you can provide any guarantees that the subset of /bin/sh features common to all current instances of /bin/sh is adequate to build a moderately demanding open source package? Or are you oriented towards kiloLOCs of test code to see which features are implemented and provide compatability a la autoconf? ++L
