Re: Golang Xen packages and the golang packaging system

2020-04-28 Thread Nick Rosbrook
> BTW the separate repo isn’t off the table. But there were some things other > Ian pointed out: After trying (and failing) to get a go module with a remote import path like `golang.xenproject.org/xenlight` defined in xen.git, I would like to circle back to the separate repo. In theory, modules

Re: Golang Xen packages and the golang packaging system

2020-04-24 Thread Nick Rosbrook
Dunlap > >>> wrote: > >>> > >>> > >>> > >>>> On Apr 23, 2020, at 12:27 PM, Ian Jackson wrote: > >>>> > >>>> Ian Jackson writes ("Re: Golang Xen packages and the golang packaging > >

Re: Golang Xen packages and the golang packaging system

2020-04-24 Thread George Dunlap
2020, at 12:27 PM, Ian Jackson wrote: >>>> >>>> Ian Jackson writes ("Re: Golang Xen packages and the golang packaging >>>> system"): >>>>> This is quite unpleasant. In particular, it makes a git tree out of >>>>> o

Re: Golang Xen packages and the golang packaging system

2020-04-23 Thread Nick Rosbrook
On Thu, Apr 23, 2020 at 1:22 PM George Dunlap wrote: > > > > On Apr 23, 2020, at 12:49 PM, George Dunlap > > wrote: > > > > > > > >> On Apr 23, 2020, at 12:27 PM, Ian Jackson wrote: > >> > >> Ian Jackson writes ("Re: Golang

Re: Golang Xen packages and the golang packaging system

2020-04-23 Thread George Dunlap
> On Apr 23, 2020, at 12:49 PM, George Dunlap wrote: > > > >> On Apr 23, 2020, at 12:27 PM, Ian Jackson wrote: >> >> Ian Jackson writes ("Re: Golang Xen packages and the golang packaging >> system"): >>> This is quite unpleasant. In

Re: Golang Xen packages and the golang packaging system

2020-04-23 Thread George Dunlap
> On Apr 23, 2020, at 12:27 PM, Ian Jackson wrote: > > Ian Jackson writes ("Re: Golang Xen packages and the golang packaging > system"): >> This is quite unpleasant. In particular, it makes a git tree out of >> output files. What will we do when someone s

Re: Golang Xen packages and the golang packaging system

2020-04-23 Thread Ian Jackson
Ian Jackson writes ("Re: Golang Xen packages and the golang packaging system"): > This is quite unpleasant. In particular, it makes a git tree out of > output files. What will we do when someone sends us patches to the > bindings ? Also, anyone who redistributes your propose

Re: Golang Xen packages and the golang packaging system

2020-04-23 Thread Ian Jackson
George Dunlap writes ("Golang Xen packages and the golang packaging system"): > So currently, our build system will install the xenlight package into > $PREFIX/share/gocode/src/golang.xenproject.org/xenlight. However, it > actually takes a bit of wrestling to get golang t

Re: Golang Xen packages and the golang packaging system

2020-04-23 Thread George Dunlap
> On Apr 22, 2020, at 7:55 PM, Nick Rosbrook wrote: > >> One question I have from the above is how the xen.git RELEASE-X.Y.Z should >> correspond to the vA.B.C in the golang package repo. >> >> The obvious answer, of course, is (A, B, C) = (X, Y, Z); that is, xen.git >> tag RELEASE-4.14.0 sh

Re: Golang Xen packages and the golang packaging system

2020-04-22 Thread Nick Rosbrook
> One question I have from the above is how the xen.git RELEASE-X.Y.Z should > correspond to the vA.B.C in the golang package repo. > > The obvious answer, of course, is (A, B, C) = (X, Y, Z); that is, xen.git tag > RELEASE-4.14.0 should create a golang package tag of v4.14.0. > > The issue with

Golang Xen packages and the golang packaging system

2020-04-22 Thread George Dunlap
So currently, our build system will install the xenlight package into $PREFIX/share/gocode/src/golang.xenproject.org/xenlight. However, it actually takes a bit of wrestling to get golang to use this location, and makes it difficult to use shared code. It would be nice if people could simply ad