> Another thing that can be done is to maintain a separate > "ports" repository, where you keep patches required to build > but that are not yet integrated in any upstream repo + any > other bits to a s/w package in a platform specific manner. > This is how FreeBSD ports work. Everyone shouldn't have to > track down patches and try merging them individually.
If the Go builders system wasn't already in place, that would have great merit, but as things stand, short of providing a better system for the Go developers to adopt (a dream, but not a very practical one - I'm not in love with Mercurial, Python or any other immense GNU-ish package), we may as well encourage everyone to use what is known to work adequately. If you feel we can do better and you are prepared to defend your case, this (or the go-plan9 google group) will be a reasonable platforms to present it. I, for one, will be willing to hear about any such option. ++L
