From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20131202193752.DE791B827@mail.bitblocks.com> References: <91774b6345d79748c720755d28a9f6ef@proxima.alt.za> <9e4fad988f611729bb064703d636be14@coraid.com> <20131202193752.DE791B827@mail.bitblocks.com> Date: Mon, 2 Dec 2013 11:57:34 -0800 Message-ID: From: Skip Tavakkolian To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=f46d04479f1145d58b04ec92979d Subject: Re: [9fans] Go and 21-bit runes (and a bit of Go status) Topicbox-Message-UUID: 8e38c2d6-ead8-11e9-9d60-3106f5b1d025 --f46d04479f1145d58b04ec92979d Content-Type: text/plain; charset=ISO-8859-1 Some coordination among people who are 9fan-gonut, 9fan-godev or 9dev would be helpful; at least it will reduce unnecessary head-scratching. On Mon, Dec 2, 2013 at 11:37 AM, Bakul Shah wrote: > On Mon, 02 Dec 2013 13:33:34 EST erik quanstrom > wrote: > > all this is moot unless we can get plan 9 integrated into go's automatic > > build system. is this doable? i have resources to make this happen if > > it is. > > One simple thing that can be done is to set up a cron job to > fetch updates and if anything changed, to rebuild and mail if > there are any essential differences from previous run. > > Requires no additional cooperation from anyone else and can > work for catching breakage early in any third party software. > > 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. > > --f46d04479f1145d58b04ec92979d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Some coordination among people who are 9fan-gonut, 9fan-go= dev or 9dev would be helpful; at least it will reduce unnecessary head-scra= tching.=A0

On= Mon, Dec 2, 2013 at 11:37 AM, Bakul Shah <bakul@bitblocks.com> wrote:
On Mon, 02 Dec 2013 13:33:= 34 EST erik quanstrom <quans= tro@labs.coraid.com> wrote:
> all this is moot unless we can get plan 9 integrated into go's aut= omatic
> build system. =A0is this doable? =A0i have resources to make this happ= en if
> it is.

One simple thing that can be done is to set up a cron job to
fetch updates and if anything changed, to rebuild and mail if
there are any essential differences from previous run.

Requires no additional cooperation from anyone else and can
work for catching breakage early in any third party software.

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.


--f46d04479f1145d58b04ec92979d--