Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

Thanks for the correction :-) On Thu, Sep 29, 2016 at 2:26 AM, Dave Cheney wrote: > s/go build/go install/g > > On Thursday, 29 September 2016 01:41:31 UTC+10, Micky wrote: >> >> go list ... >> go build ... >> >> It will build only if it it needs to! Otherwise add -a to force.

Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

On Wednesday, September 28, 2016 at 2:31:44 PM UTC-7, andrey mirtchovski wrote: > > > If I want to start from the executables in $GOPATH/bin and recompile > only > > those, is there a way to tell what package an executable comes from so I > can > > easily automate the process? E.g.

Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

> go list -f '{{.ImportPath}}: {{.Target}}' all | grep $GOPATH/bin mistyped GOPATH, sorry. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

> If I want to start from the executables in $GOPATH/bin and recompile only > those, is there a way to tell what package an executable comes from so I can > easily automate the process? E.g. goimports is the result of "go install > golang.org/x/tools/cmd/goimports", etc. you can do it by listing

Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

s/go build/go install/g On Thursday, 29 September 2016 01:41:31 UTC+10, Micky wrote: > > go list ... > go build ... > > It will build only if it it needs to! Otherwise add -a to force. > > On Wed, Sep 28, 2016 at 8:30 PM, Tim K > wrote: > >> OK, so all that should happen is

Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

If I want to start from the executables in $GOPATH/bin and recompile only those, is there a way to tell what package an executable comes from so I can easily automate the process? E.g. goimports is the result of "go install golang.org/x/tools/cmd/goimports", etc. On Wednesday, September 28,

Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

use 'go list' to see which packages you have installed and which may need upgrading (they all will, in the end). 'go help packages' will tell you the difference between 'go list std', 'go list all', and also how to query individual folders inside GOPATH. "go build -i" will ensure that

Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

go list ... go build ... It will build only if it it needs to! Otherwise add -a to force. On Wed, Sep 28, 2016 at 8:30 PM, Tim K wrote: > OK, so all that should happen is just re-install the binaries in > $GOPATH/bin. Does anyone have any tips or helper scripts that help

[go-nuts] Re: do packages need to be recompiled when Go is upgraded?

OK, so all that should happen is just re-install the binaries in $GOPATH/bin. Does anyone have any tips or helper scripts that help automate re-installing all these binaries? There's a pile of them which makes it a bit difficult to find out what exact package path they came from so they can be