sm
/
gorigin
1
0
Fork 0
Code Issues Pull Requests Activity
what is the origin of that go binary? http://mcquay.me/gorigin/
10 Commits 1 Branch 0 Tags 28 KiB
Go 100%
Go to file
Stephen McQuay 34cdece6ae
report as we find them 
this is in prep to make process concurrent
 		2017-02-09 08:31:37 -08:00
license updated license 2015-06-22 19:40:41 -07:00
main.go report as we find them 2017-02-09 08:31:37 -08:00
readme.md added simple readme 2015-03-05 07:03:09 -08:00

readme.md

gorigin

Have you ever peered into $GOPATH/bin only to wonder where all that stuff came from?

As someone who originally came from scripting languages where one could trivially peer into an 'executable' using an editor, the origin of binaries in that folder (specifically if GOPATH=~) was completely opaque to me. Not any more!

gorigin helps shed light on this by creating a list of binaries in all the bin folders in the GOPATH and marching through all the src folders in the GOPATH and reporting when a go package with a package name of main matches.