On Thu, Sep 5, 2019 at 10:18 PM Jan Mercl <0xj...@gmail.com> wrote:
> `go get` should do just one thing and do it well. Automagically
> adjusting `go.mod` if one is found in the current directory (or in any
> of its parents) when outside $GOPATH is IMO neither of that. Or it
> should be enabled by
On Thu, Sep 5, 2019 at 9:22 PM Jan Mercl <0xj...@gmail.com> wrote:
>
> > Running 'go get ...' inside a module can add indirect dependencies to
> > go.mod.
>
> I'm surprised. There's probably some rationale behind `go get` having
> such side effects. Can anyone please shed some light on this?
$ go
On Thu, Sep 5, 2019 at 3:28 PM Tamás Gulácsi wrote:
> Ain't Go 1.13's "go get -u" does exactly this?
> And the old behaviour with "go get -u all" ?
>
Thanks for the input but:
> I cannot use 'go get -u -t -d ./...' here because that brings in the
>> indirect dependency 'goB' into my go.mod.
>>
>
On Thu, Sep 5, 2019 at 4:33 AM t hepudds wrote:
> To upgrade your direct dependencies to their latest release (with your
> indirect dependencies using versions selected based on the requirements of
> your direct dependencies), this should work in most cases:
>
> go get $(go list -f '{{if not (o
