On 13 July 2015 at 19:04, aconway <acon...@redhat.com> wrote: > On Mon, 2015-07-13 at 18:28 +0100, Robbie Gemmell wrote: >> On 13 July 2015 at 16:23, aconway <acon...@redhat.com> wrote: >> > On Mon, 2015-07-13 at 13:03 +0100, Robbie Gemmell wrote: >> > > I don't really know much about Go, so I mainly have questions >> > > rather >> > > than answers. >> > > >> > > - What would actually be included in this 'qpid-proton-go' repo >> > > vs >> > > the >> > > existing qpid-proton repo? >> > >> > The contents of proton-c/bindings/go on branch "go1". Basically the >> > Go >> > binding source code. >> > >> > > - Have you looked into how other Apache projects are supporting >> > > "go >> > > get", if there are any, to see what do they do? >> > >> > Nope, good point. I've looked at a bunch of google and github >> > projects, >> > but all pure Go so the tools Just Work. Anyone know of other mixed >> > -language projects with a go component? >> > >> > > I'm not sure how well it would go down with infra to be routinely >> > > 'distributing' things directly out of the repo. >> > >> > I'm pretty sure they're OK with distributing source code out of the >> > repo :) Go distributes everything as pure source, so no unusual >> > use of >> > the repo is implied. >> >> I mainly meant that developers and interested folks using the repo to >> get at the source for inspection and modification isn't necessarily >> considered the same as using it as a regular entry point for most >> users. For example, we use the mirror system for our actual [source] >> releases. That said, if we are discussing a fairly small binding that >> probably isn't much of an issue, and as I wondered, perhaps the >> github >> mirror of the repo might be a useful tool there. >> > +1, we could certainly do that. That doesn't solve the structural > problems but I'll keep digging and head scratching. >
I meant the mirror of any new repo needed as well, in case that wasn't clear. >> > I have "go get" *almost* working directly out of >> > the ASF repo now, but I can't work around all the glitches - in >> > particular the documentation browser is a mess. If I could I would >> > rather keep it all in the same repo. >> > >> > > Might be worth >> > > discussing with infra. Perhaps we could point folks at the GitHub >> > > mirror to alleviate that? Not sure if there are path issues >> > > involved >> > > with that though. Somewhat looping back to 'what do other >> > > projects >> > > do?' again. >> > >> > Good point, I'll ask around and on infra, I may be missing >> > something. >> > If anyone's interested in brainstorming about the proper way to do >> > this >> > (esp. anyone who's done Go work) I'd be happy to go over the issues >> > in >> > painful detail. >> > >> > > On 10 July 2015 at 16:34, aconway <acon...@redhat.com> wrote: >> > > > I would like to create a separte git repo for the proton Go >> > > > binding. >> > > > >> > > > Go provides "go get" to grab online go source libraries, based >> > > > on >> > > > cloning repos. The go tools assume that each go project has its >> > > > own >> > > > repo. I have tried to make this work directly from the proton >> > > > repo >> > > > but >> > > > it is a mess and doesn't work properly. >> > > > >> > > > Any objections or suggestions? >> > > > >> > > > Anyone got pointers to speed me thru the apache infra process? >> > > > >> > > > Cheers, >> > > > Alan.
