How precisely would we ship multiple versions? We still have only 1 orig
tarball, and one upstream branch.

I updated the document: I think we need to switch from packaging upstream
repositories to packaging upstream modules. I think the “multiple versions”
situation doesn’t change: we can ship multiple major versions today (as
long as they use a different import path, which is customary and even
required by vgo), and can do the same with vgo.

On Fri, Feb 23, 2018 at 1:29 PM, Shengjing Zhu <i...@zhsj.me> wrote:

> On Thu, Feb 22, 2018 at 3:34 PM, Michael Stapelberg
> <stapelb...@debian.org> wrote:
> > Here are my thoughts on what this means for us (so far):
> > https://docs.google.com/document/d/1XpiOBCLgqG8pKcz3cb6q45mDevCSO
> Tb3AssSUzaujKI/edit
> >
> > Please feel free to comment/make suggestions either on the document or in
> > this email thread.
> >
> > Eventually (likely by the time Go actually ships this), I’ll freeze the
> > document and add it to our website.
> >
> >
>
> In the new posts from Russ https://research.swtch.com/vgo-repro
> `vgo build` creates the binary with building info embedded. With
> `goversion -mh` one can view the version of modules used when
> building. dh-golang's Built-Using is similar to this.
>
> I find vgo puts module src in `$GOPATH/v/path@version`. We can benefit
> from this, to ship multiple versions of a module together.
>
> --
> Best regards,
> Shengjing Zhu
>



-- 
Best regards,
Michael
_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to