> 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
Dunlap
> >>> wrote:
> >>>
> >>>
> >>>
> >>>> On Apr 23, 2020, at 12:27 PM, Ian Jackson wrote:
> >>>>
> >>>> Ian Jackson writes ("Re: Golang Xen packages and the golang packaging
> >
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
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
> 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
> 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
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
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 to use this location, an
> 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
> 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
10 matches
Mail list logo
