Re: [go-nuts] Go get -f still checking VCS

2017-10-04 Thread alexandre . ferrieux
On Tuesday, October 3, 2017 at 11:20:11 AM UTC+2, Jakob Borg wrote: > > On 3 Oct 2017, at 10:17, alexandre...@gmail.com wrote: > > > > Thanks. However, "go get -t" still complains about "missing Git > command". Indeed, on that machine I intentionally don't use any VCS (just > a source tarba

Re: [go-nuts] Go get -f still checking VCS

2017-10-03 Thread alexandre . ferrieux
On Monday, October 2, 2017 at 1:26:31 PM UTC+2, Jakob Borg wrote: > > The documentation for the -f flags says: > > > The -f flag, valid only when -u is set, forces get -u not to verify that > > each package has been checked out from the source control repository > > implied by its import path.

[go-nuts] Re: Go get -f still checking VCS

2017-10-02 Thread alexandre . ferrieux
Bump -- this looks like a very basic misbehavior, the "-f" flag simply ignored... any taker ? On Sunday, October 1, 2017 at 6:16:58 AM UTC+2, alexandre...@gmail.com wrote: > > Hi, > > I'm trying to build quic-go (Go implementation of the QUIC protocol > https://github.com/lucas-clemente/quic-go

[go-nuts] Go get -f still checking VCS

2017-09-30 Thread alexandre . ferrieux
Hi, I'm trying to build quic-go (Go implementation of the QUIC protocol https://github.com/lucas-clemente/quic-go ). As per the project's instructions, the first step is: go get -t -u ./... But doing so results in a wealth of fatal errors like: package quic-go-master: directory "/home/al