On Tue, Aug 28, 2012 at 05:36:58PM +0200, Lucio De Re wrote: > > Sure, feel free to make something that isn't shitty, there's plenty > out there that can be improved. The machinery to install Go (from > sources) is hardly the most important amongst them. >
The Go team has already explicitly stated they are note interested in a better build system. I don't know if it's plain NIH or a secret bash fetish, but they're not buying. Improving software is not a zero-sum game; Go development is not a closed system. The build system can be improved without impeding other progress. > Solution: replace > the #!/bin/sh with #!/usr/bin/env -c /bin/bash. Why not? Because there are plenty of systems out there without env or bash. > I may > misremember, but before the Go tool was released, the Plan 9 release > managed to get itself compiled using ape/sh. As far as I can tell, > the dependence isn't in Bash features as much as in the consistency > across Bash versions. > ...which is another unproved assumption.
