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 prerequisite library dependencies are also installed, which will populate the entire pkg/* directory. On Wed, Sep 28, 2016 at 9:30 AM, Tim K <tim.ka...@gmail.com> 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 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 rebuilt. > > Thanks! > > > On Wednesday, September 28, 2016 at 7:43:18 AM UTC-7, Chris Hines wrote: >> >> I'm pretty sure that the last few versions of Go (since 1.5 maybe) are >> smart enough to do it automatically. I believe the .o files in the pkg tree >> have the compiler version embedded in their meta data for this purpose. > > -- > 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 golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
