The fate of x/vgo package

311 views
Skip to first unread message

Florin Pățan

unread,
Aug 4, 2018, 6:10:57 PM8/4/18
to golang-dev
Hi,


Now that the Go modules proposal has been accepted, I would like to get more information about the state of x/vgo repo and the standalone tool itself.

From what I can tell, it's been abandoned/deprecated. In this case should it also get a notice or be completely removed in order to remove the confusion over its status?

Will Go 1.10 receive any further Go modules support? What will happen with the current module support in 1.10 (and iirc 1.9) after 1.11 is released? Do we need to support anything special for those versions?

This is of particular interest for those of us who do not rely on the "go/*" packages to build tooling for Go, or teach people to work with Go.

If this has been discussed in a different place, my apologies for the noise, a link to that place would be appreciated.

Thank you.


Kind regards,
Florin

Brad Fitzpatrick

unread,
Aug 4, 2018, 10:49:11 PM8/4/18
to Florin Patan, golang-dev
I think Russ mentioned that the "go" repo is now the main upstream repo for modules work, but vgo would continue to get synced from upstream, so people can help test module support at the bleeding edge. That'll probably only continue for 6-12 months.


--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Russ Cox

unread,
Aug 6, 2018, 12:23:32 PM8/6/18
to Florin Pățan, golang-dev
[sorry, reply all this time]

I'm not entirely sure what you are asking, so let me know if this doesn't answer it. 

The main repo is now the source of truth for Go module support.
The vgo repo is now auto-generated from the main repo by running update.bash.

The vgo command is meant to allow Go 1.10 users to try modules.
It should behave exactly the same as the Go 1.11 go command,
except that GO111MODULE defaults to on (not auto), and it does
not run 'go vet' during 'go test' when using a Go 1.10 GOROOT.

We intend to run update.bash at each release milestone, but we missed
last week's update for go1.11beta3. I'll send that out shortly, along with
an update to the README.md.

I expect that vgo will continue to be updated alongside point releases of Go 1.11,
to continue to allow Go 1.10 users to try modules as they exist in Go 1.11.

Best,
Russ

Florin Pățan

unread,
Aug 6, 2018, 12:40:02 PM8/6/18
to Russ Cox, golang-dev
Hi Russ,

Yes, that covers it, thank you for your reply and clarification on this.


Kind regards,
Florin
Reply all
Reply to author
Forward
0 new messages