From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9c0543674fa8e439596fc14d43f6d9ea@proxima.alt.za>
To: 9fans@9fans.net
From: Lucio De Re <lucio@proxima.alt.za>
Date: Tue, 28 Aug 2012 18:05:04 +0200
In-Reply-To: <20120828153548.GC11005@intma.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] rc vs sh
Topicbox-Message-UUID: b1585cbe-ead7-11e9-9d60-3106f5b1d025

>> 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.

Worth a try, though!  There is very little shell code left in the Go
release.  Maybe I'll give it a try on my pristine NetBSD machine.

But note that even if it does work, it is still not possible for the
Go Team to release the scripts as /bin/sh scripts because, as you have
clearly not yet grasped, not all /bin/sh instances out there can be
shown to be compatible with any one /bin/sh script, not matter how
"portable"!

Maybe the following illustration will help: Given Unix, Plan 9 and
Windows as target platforms, how does one go about releasing a single
build environment for all of them that on invocation automatically
produces the target package?  I didn't give it a lot of thought, but
it seems to me that the totally general build (bootstrap?) operation
for this purpose does not (and, it seems to me, cannot) exist.

++L