We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go version
vgo version go version go1.10.1 linux/amd64 vgo:2018-02-20.1
go env
vgo env GOARCH="amd64" GOBIN="" GOCACHE="/home/matthew/.cache/go-build" GOEXE="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOOS="linux" GOPATH="/home/matthew/src/Go_external_1.10.1" GOPROXY="" GORACE="" GOROOT="/home/matthew/src/golang/go1.10.1" GOTMPDIR="" GOTOOLDIR="/home/matthew/src/golang/go1.10.1/pkg/tool/linux_amd64" GCCGO="gccgo" CC="gcc" CXX="g++" CGO_ENABLED="1" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build416094540=/tmp/go-build -gno-record-gcc-switches" VGOMODROOT="/home/matthew/tmp/foo"
mkdir -p tmp/foo cd !!$ echo 'module foo' > go.mod vgo get goshawkdb.io/common
vgo: finding goshawkdb.io/common v1.0.0
vgo get goshawkdb.io/common: unknown VCS, Repo: hg, https://src.goshawkdb.io/common
Now, this works fine with normal go get and the meta header is there correctly:
curl https://goshawkdb.io/common
<html> <head> <meta name="go-import" content="goshawkdb.io/common hg https://src.goshawkdb.io/common"/> <META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"> </head> </html>
I suspect this may be classed as a dupe of #25074 but that issue isn't enormously clear to me ;)
The other thing worth pointing out is that hgweb.cgi is probably the most common way of putting an http interface on hg repos. https://www.mercurial-scm.org/wiki/HgWebDirStepByStep an example of which is https://src.goshawkdb.io/common Note that this does provide tags (https://src.goshawkdb.io/common/tags and even rss: https://src.goshawkdb.io/common/rss-tags) and features such as tarballs of specific tags (eg https://src.goshawkdb.io/common/archive/goshawkdb_0.3.1.tar.gz) and even revisions (eg https://src.goshawkdb.io/common/archive/458b975cb054.tar.gz). Point is, you don't have to fall back to cloning the whole repo if you can detect that you're talking to hgweb.cgi
The text was updated successfully, but these errors were encountered:
Yep, I think it is. Russ is working on a number of fixes to vgo get this week, so hopefully this will get better soon.
vgo get
Sorry, something went wrong.
No branches or pull requests
What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?What did you do?
What did you expect to see?
What did you see instead?
Now, this works fine with normal go get and the meta header is there correctly:
I suspect this may be classed as a dupe of #25074 but that issue isn't enormously clear to me ;)
The other thing worth pointing out is that hgweb.cgi is probably the most common way of putting an http interface on hg repos. https://www.mercurial-scm.org/wiki/HgWebDirStepByStep an example of which is https://src.goshawkdb.io/common Note that this does provide tags (https://src.goshawkdb.io/common/tags and even rss: https://src.goshawkdb.io/common/rss-tags) and features such as tarballs of specific tags (eg https://src.goshawkdb.io/common/archive/goshawkdb_0.3.1.tar.gz) and even revisions (eg https://src.goshawkdb.io/common/archive/458b975cb054.tar.gz). Point is, you don't have to fall back to cloning the whole repo if you can detect that you're talking to hgweb.cgi
The text was updated successfully, but these errors were encountered: